Remote MCP · Endpoint
xyz.chainverdict/chainverdict MCP server
No. xyz.chainverdict/chainverdict answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://chainverdict.xyz/mcp
The last check completed an MCP handshake.
- Registry name
- xyz.chainverdict/chainverdict
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 381 ms
- Tools exposed
- 20 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Pay-per-call x402 checks before an agent moves money: token safety, wallet risk, identifiers.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 381 ms |
| 1 day ago | Handshake completed | 321 ms |
| 2 days ago | Handshake completed | 315 ms |
| 3 days ago | Handshake completed | 140 ms |
| 4 days ago | Handshake completed | 136 ms |
| 5 days ago | Handshake completed | 344 ms |
| 6 days ago | Handshake completed | 183 ms |
| 8 days ago | Handshake completed | 242 ms |
| 11 days ago | Handshake completed | 133 ms |
| 13 days ago | Handshake completed | 153 ms |
| 15 days ago | Handshake completed | 180 ms |
| 18 days ago | Handshake completed | 331 ms |
| 20 days ago | Handshake completed | 147 ms |
| 22 days ago | Handshake completed | 306 ms |
| 24 days ago | Handshake completed | 157 ms |
| 26 days ago | Handshake completed | 157 ms |
| 27 days ago | Handshake completed | 156 ms |
| 28 days ago | Handshake completed | 348 ms |
| 29 days ago | Handshake completed | 307 ms |
The last 19 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 xyz.chainverdict/chainverdict and makes no claim about it beyond what these checks measured.