Remote MCP · Endpoint

Picksly MCP server

No. Picksly answered an MCP handshake 39 minutes ago.

UpLast checked 39 minutes ago

Server URL

https://picksly.fr/api/mcp

The last check completed an MCP handshake.

Registry name
fr.picksly/picksly
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
104 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Best phone, tablet, laptop or smartwatch for your profile and budget: lab scores, live prices.
Listing
From the official MCP registry (active).
Recent checks of Picksly
CheckedResultHandshake
39 minutes agoHandshake completed104 ms
3 days agoHandshake completed407 ms
13 days agoHandshake completed196 ms
13 days agoHandshake completed108 ms
15 days agoHandshake completed127 ms
16 days agoHandshake completed117 ms
17 days agoHandshake completed140 ms
18 days agoHandshake completed114 ms
18 days agoHandshake completed109 ms
20 days agoHandshake completed127 ms
22 days agoHandshake completed113 ms
25 days agoHandshake completed112 ms
27 days agoHandshake completed154 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Picksly and makes no claim about it beyond what these checks measured.