Remote MCP · Endpoint
sunpeak MCP server
No. sunpeak answered an MCP handshake 7 hours ago.
Up · key neededLast checked 7 hours ago
Server URL
https://doc2mcp.site/api/mcp/c97f81d9-55ac-4b5d-b64d-6e3c04c6eb36/mcp
The handshake completes, but listing its tools needs credentials.
- Registry name
- io.github.doc2mcp/sunpeak
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 324 ms
- Tools exposed
- Behind credentials
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- MCP server for sunpeak documentation, generated by doc2mcp.
- Repository
- https://github.com/doc2mcp/doc2mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 7 hours ago | Handshake completed | 324 ms |
| 2 days ago | Handshake completed | 340 ms |
| 4 days ago | Handshake completed | 354 ms |
| 5 days ago | Handshake completed | 486 ms |
| 7 days ago | Handshake completed | 409 ms |
| 8 days ago | Handshake completed | 372 ms |
| 9 days ago | Handshake completed | 338 ms |
| 12 days ago | Handshake completed | 330 ms |
| 13 days ago | Handshake completed | 322 ms |
| 15 days ago | Handshake completed | 412 ms |
| 16 days ago | Handshake completed | 300 ms |
| 17 days ago | Handshake completed | 365 ms |
| 19 days ago | Handshake completed | 323 ms |
| 19 days ago | Handshake completed | 340 ms |
| 20 days ago | Handshake completed | 378 ms |
| 21 days ago | Handshake completed | 314 ms |
| 23 days ago | Handshake completed | 853 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 sunpeak and makes no claim about it beyond what these checks measured.