Remote MCP · Endpoint
AnchorRegistry MCP server
No. AnchorRegistry answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.anchorregistry.ai/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.AnchorRegistry/ar-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 684 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- On-chain provenance lookup for AnchorRegistry. Resolve AR-IDs, hashes, and full trees. Authless.
- Website
- https://anchorregistry.com/
- Repository
- https://github.com/anchorregistry/ar-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 684 ms |
| 2 days ago | Handshake completed | 673 ms |
| 4 days ago | Handshake completed | 320 ms |
| 5 days ago | Handshake completed | 584 ms |
| 7 days ago | Handshake completed | 568 ms |
| 8 days ago | Handshake completed | 741 ms |
| 9 days ago | Handshake completed | 351 ms |
| 12 days ago | Handshake completed | 521 ms |
| 13 days ago | Handshake completed | 494 ms |
| 15 days ago | Handshake completed | 650 ms |
| 16 days ago | Handshake completed | 807 ms |
| 18 days ago | Handshake completed | 316 ms |
| 19 days ago | Handshake completed | 271 ms |
| 20 days ago | Handshake completed | 639 ms |
| 20 days ago | Handshake completed | 452 ms |
| 21 days ago | Handshake completed | 488 ms |
| 22 days ago | Handshake completed | 742 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 AnchorRegistry and makes no claim about it beyond what these checks measured.