Remote MCP · Endpoint
developers MCP server
No. developers answered an MCP handshake 2 hours ago.
Up · key neededLast checked 2 hours ago
Server URL
https://www.doc2mcp.site/api/mcp/f335b6a5-ec4b-4b0f-9f19-ef5af221aed2/mcp
The handshake completes, but listing its tools needs credentials.
- Registry name
- io.github.doc2mcp/developers
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 331 ms
- Tools exposed
- Behind credentials
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- MCP server for developers documentation, generated by doc2mcp.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 331 ms |
| 2 days ago | Handshake completed | 273 ms |
| 4 days ago | Handshake completed | 264 ms |
| 5 days ago | Handshake completed | 287 ms |
| 7 days ago | Handshake completed | 306 ms |
| 8 days ago | Handshake completed | 264 ms |
| 9 days ago | Handshake completed | 289 ms |
| 12 days ago | Handshake completed | 309 ms |
| 13 days ago | Handshake completed | 267 ms |
| 15 days ago | Handshake completed | 270 ms |
| 17 days ago | Handshake completed | 263 ms |
| 18 days ago | Handshake completed | 255 ms |
| 19 days ago | Handshake completed | 303 ms |
| 20 days ago | Handshake completed | 279 ms |
| 20 days ago | Handshake completed | 247 ms |
| 21 days ago | Handshake completed | 246 ms |
| 23 days ago | Handshake completed | 242 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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 developers and makes no claim about it beyond what these checks measured.