Remote MCP · Endpoint
developer MCP server
No. developer answered an MCP handshake 1 hour ago.
Up · key neededLast checked 1 hour ago
Server URL
https://doc2mcp.site/api/mcp/c7dd7af1-84b9-4bc3-a3e8-0b3a324c8413/mcp
The handshake completes, but listing its tools needs credentials.
- Registry name
- io.github.doc2mcp/developer
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 358 ms
- Tools exposed
- Behind credentials
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- MCP server for developer documentation, generated by doc2mcp.
- Repository
- https://github.com/doc2mcp/doc2mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 358 ms |
| 1 day ago | Handshake completed | 324 ms |
| 2 days ago | Handshake completed | 328 ms |
| 3 days ago | Handshake completed | 306 ms |
| 4 days ago | Handshake completed | 322 ms |
| 5 days ago | Handshake completed | 332 ms |
| 6 days ago | Handshake completed | 506 ms |
| 9 days ago | Handshake completed | 305 ms |
| 11 days ago | Handshake completed | 322 ms |
| 14 days ago | Handshake completed | 483 ms |
| 16 days ago | Handshake completed | 415 ms |
| 18 days ago | Handshake completed | 318 ms |
| 20 days ago | Handshake completed | 307 ms |
| 22 days ago | Handshake completed | 276 ms |
| 24 days ago | Handshake completed | 305 ms |
| 26 days ago | Handshake completed | 474 ms |
| 28 days ago | Handshake completed | 332 ms |
| 29 days ago | Handshake completed | 327 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 developer and makes no claim about it beyond what these checks measured.