Remote MCP · Endpoint

Assay: settlement verification MCP server

No. Assay: settlement verification answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://fomox.io/api/assay/mcp

The last check completed an MCP handshake.

Registry name
io.fomox/assay
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
213 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Verify crypto payments really settled and how much arrived. 20 chains. Read only, no API key.
Listing
From the official MCP registry (active).
Recent checks of Assay: settlement verification
CheckedResultHandshake
6 hours agoHandshake completed213 ms
9 days agoHandshake completed362 ms
10 days agoHandshake completed3.18 s
11 days agoHandshake completed323 ms
12 days agoHandshake completed217 ms
14 days agoHandshake completed230 ms
15 days agoHandshake completed214 ms
15 days agoHandshake completed244 ms
17 days agoHandshake completed341 ms
19 days agoHandshake completed221 ms
22 days agoHandshake completed984 ms
24 days agoHandshake completed577 ms
26 days agoHandshake completed258 ms
28 days agoHandshake completed671 ms

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

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