Remote MCP · Endpoint

Stablecoin Scanner MCP server

No. Stablecoin Scanner answered an MCP handshake 6 hours ago.

UpLast checked 6 hours 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
178 ms
Tools exposed
8 tools
Uptime, last 30 days
92.9% 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
6 hours agoHandshake completed178 ms
9 days agoHandshake completed166 ms
10 days agoHandshake completed175 ms
11 days agoHandshake completed219 ms
12 days agoFailed - the request timed out—
14 days agoHandshake completed184 ms
14 days agoHandshake completed411 ms
15 days agoHandshake completed165 ms
17 days agoHandshake completed434 ms
19 days agoHandshake completed435 ms
22 days agoHandshake completed163 ms
24 days agoHandshake completed426 ms
26 days agoHandshake completed428 ms
28 days agoHandshake completed422 ms

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

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.