Remote MCP · Endpoint

POAScan MCP server

No. POAScan answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://poascan.io/mcp

The last check completed an MCP handshake.

Registry name
io.github.jakegallen/poascan
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
181 ms
Tools exposed
52 tools
Uptime, last 30 days
76.9% from 13 checks
Described by its publisher as
Read-only Proof of Agent explorer: epochs, rewards, holders, swaps and agent census. No auth.
Listing
From the official MCP registry (active).
Recent checks of POAScan
CheckedResultHandshake
9 hours agoHandshake completed181 ms
4 days agoHandshake completed174 ms
14 days agoFailed - the check failed for an unclassified reason—
15 days agoHandshake completed239 ms
15 days agoFailed - the check failed for an unclassified reason—
17 days agoHandshake completed152 ms
18 days agoFailed - the request timed out—
19 days agoHandshake completed178 ms
20 days agoHandshake completed190 ms
21 days agoHandshake completed131 ms
23 days agoHandshake completed108 ms
26 days agoHandshake completed102 ms
28 days agoHandshake completed124 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 11 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 POAScan and makes no claim about it beyond what these checks measured.