Remote MCP · Endpoint
MCP Registry Server MCP server
No. MCP Registry Server answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://registry.run.mcp.com.ai/mcp
The last check completed an MCP handshake.
- Registry name
- ai.com.mcp/registry
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 278 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Publish and discover MCP servers via the official MCP Registry. Powered by HAPI MCP server.
- Website
- https://run.mcp.com.ai/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 278 ms |
| 1 day ago | Handshake completed | 154 ms |
| 3 days ago | Handshake completed | 173 ms |
| 3 days ago | Handshake completed | 148 ms |
| 4 days ago | Handshake completed | 154 ms |
| 5 days ago | Handshake completed | 181 ms |
| 7 days ago | Handshake completed | 188 ms |
| 10 days ago | Handshake completed | 148 ms |
| 12 days ago | Handshake completed | 45 ms |
| 14 days ago | Handshake completed | 65 ms |
| 17 days ago | Handshake completed | 78 ms |
| 19 days ago | Handshake completed | 541 ms |
| 21 days ago | Handshake completed | 337 ms |
| 23 days ago | Handshake completed | 57 ms |
| 25 days ago | Handshake completed | 168 ms |
| 26 days ago | Handshake completed | 177 ms |
| 28 days ago | Handshake completed | 265 ms |
| 29 days ago | Handshake completed | 177 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 MCP Registry Server and makes no claim about it beyond what these checks measured.