Remote MCP · Endpoint

TokenVerdict MCP server

No. TokenVerdict answered an MCP handshake 30 minutes ago.

UpLast checked 30 minutes ago

Server URL

https://api.youraitools.co/tokenverdict/mcp

The last check completed an MCP handshake.

Registry name
co.youraitools/tokenverdict
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
257 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Base token safety check: simulated buy/transfer/sell, owner powers, liquidity. By Crypto Money Maker
Listing
From the official MCP registry (active).
Recent checks of TokenVerdict
CheckedResultHandshake
30 minutes agoHandshake completed257 ms
3 days agoHandshake completed113 ms
13 days agoHandshake completed119 ms
14 days agoHandshake completed435 ms
15 days agoHandshake completed290 ms
16 days agoHandshake completed77 ms
17 days agoHandshake completed239 ms
18 days agoHandshake completed284 ms
19 days agoHandshake completed172 ms
21 days agoHandshake completed375 ms
23 days agoHandshake completed254 ms
25 days agoHandshake completed144 ms
27 days agoHandshake completed131 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

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 TokenVerdict and makes no claim about it beyond what these checks measured.