Remote MCP · Endpoint
Chainstack MCP server
No. Chainstack answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.chainstack.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.chainstack/chainstack
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 764 ms
- Tools exposed
- 23 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Deploy and manage blockchain nodes across 70+ protocols, search docs, request testnet funds.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 764 ms |
| 19 hours ago | Handshake completed | 726 ms |
| 2 days ago | Handshake completed | 812 ms |
| 3 days ago | Handshake completed | 722 ms |
| 4 days ago | Handshake completed | 730 ms |
| 5 days ago | Handshake completed | 793 ms |
| 6 days ago | Handshake completed | 719 ms |
| 8 days ago | Handshake completed | 731 ms |
| 10 days ago | Handshake completed | 728 ms |
| 13 days ago | Handshake completed | 1.25 s |
| 15 days ago | Handshake completed | 281 ms |
| 17 days ago | Handshake completed | 754 ms |
| 19 days ago | Handshake completed | 750 ms |
| 21 days ago | Handshake completed | 815 ms |
| 23 days ago | Handshake completed | 766 ms |
| 25 days ago | Handshake completed | 778 ms |
| 27 days ago | Handshake completed | 772 ms |
| 28 days ago | Handshake completed | 284 ms |
| 29 days ago | Handshake completed | 782 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 30.
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 Chainstack and makes no claim about it beyond what these checks measured.