Remote MCP · Endpoint

Picodev Lab MCP server

No. Picodev Lab answered an MCP handshake 45 minutes ago.

UpLast checked 45 minutes ago

Server URL

https://lab.picodev.fr/mcp

The last check completed an MCP handshake.

Registry name
io.github.PICODEV-SAS/picodev-lab
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
290 ms
Tools exposed
23 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Arduino benches simulated in the browser: sessions, sketch push, simulation, tests, challenges.
Listing
From the official MCP registry (active).
Recent checks of Picodev Lab
CheckedResultHandshake
45 minutes agoHandshake completed290 ms
3 days agoHandshake completed310 ms
12 days agoHandshake completed285 ms
13 days agoHandshake completed276 ms
14 days agoHandshake completed277 ms
15 days agoHandshake completed343 ms
16 days agoHandshake completed278 ms
17 days agoHandshake completed272 ms
18 days agoHandshake completed283 ms
19 days agoHandshake completed278 ms
22 days agoHandshake completed285 ms
25 days agoHandshake completed533 ms
27 days agoHandshake completed274 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 Picodev Lab and makes no claim about it beyond what these checks measured.