Remote MCP · Endpoint

Stablecoin Scanner MCP server

No. Stablecoin Scanner answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://stablescan.achivx.com/mcp

The last check completed an MCP handshake.

Registry name
com.achivx/stablescan
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
163 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Stablecoin risk for agents: freezes, OFAC, exposure, allowances, transfers, graph. 7 chains.
Listing
From the official MCP registry (active).
Recent checks of Stablecoin Scanner
CheckedResultHandshake
1 hour agoHandshake completed163 ms
2 days agoHandshake completed426 ms
4 days agoHandshake completed428 ms
6 days agoHandshake completed422 ms
8 days agoHandshake completed169 ms
10 days agoHandshake completed401 ms
13 days agoHandshake completed399 ms
14 days agoHandshake completed402 ms
16 days agoHandshake completed420 ms
17 days agoHandshake completed482 ms
18 days agoHandshake completed389 ms
21 days agoHandshake completed396 ms
22 days agoHandshake completed390 ms
24 days agoHandshake completed228 ms

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

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