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).
Recent checks of xyz.chainverdict/chainverdict
CheckedResultHandshake
1 hour agoHandshake completed381 ms
1 day agoHandshake completed321 ms
2 days agoHandshake completed315 ms
3 days agoHandshake completed140 ms
4 days agoHandshake completed136 ms
5 days agoHandshake completed344 ms
6 days agoHandshake completed183 ms
8 days agoHandshake completed242 ms
11 days agoHandshake completed133 ms
13 days agoHandshake completed153 ms
15 days agoHandshake completed180 ms
18 days agoHandshake completed331 ms
20 days agoHandshake completed147 ms
22 days agoHandshake completed306 ms
24 days agoHandshake completed157 ms
26 days agoHandshake completed157 ms
27 days agoHandshake completed156 ms
28 days agoHandshake completed348 ms
29 days agoHandshake completed307 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.