Remote MCP · Endpoint

pmndrs docs MCP server

No. pmndrs docs answered an MCP handshake 37 minutes ago.

UpLast checked 37 minutes ago

Server URL

https://docs.pmnd.rs/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.pmndrs/docs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
210 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Search and read the docs and examples of react-three-fiber, drei, zustand, jotai... from your agent
Listing
From the official MCP registry (active).
Recent checks of pmndrs docs
CheckedResultHandshake
37 minutes agoHandshake completed210 ms
3 days agoHandshake completed386 ms
13 days agoHandshake completed1.08 s
13 days agoHandshake completed256 ms
15 days agoHandshake completed172 ms
16 days agoHandshake completed164 ms
17 days agoHandshake completed163 ms
18 days agoHandshake completed196 ms
18 days agoHandshake completed154 ms
20 days agoHandshake completed205 ms
22 days agoHandshake completed150 ms
25 days agoHandshake completed910 ms
27 days agoHandshake completed193 ms
30 days agoHandshake completed170 ms

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

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 pmndrs docs and makes no claim about it beyond what these checks measured.