Remote MCP · Endpoint

io.github.f-tiger/agiscorecard-web3-calls MCP server

No. io.github.f-tiger/agiscorecard-web3-calls answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://calls.agiscorecard.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.f-tiger/agiscorecard-web3-calls
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
361 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Decode supported token calls and flag recipient or amount mismatches; no wallet or safety verdict.
Listing
From the official MCP registry (active).
Recent checks of io.github.f-tiger/agiscorecard-web3-calls
CheckedResultHandshake
2 hours agoHandshake completed361 ms
1 day agoHandshake completed119 ms
3 days agoHandshake completed95 ms
3 days agoHandshake completed149 ms
4 days agoHandshake completed284 ms
5 days agoHandshake completed98 ms
7 days agoHandshake completed154 ms
10 days agoHandshake completed178 ms
12 days agoHandshake completed67 ms
15 days agoHandshake completed192 ms
17 days agoHandshake completed170 ms
19 days agoHandshake completed398 ms
21 days agoHandshake completed175 ms
23 days agoHandshake completed208 ms
25 days agoHandshake completed40 ms

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

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 io.github.f-tiger/agiscorecard-web3-calls and makes no claim about it beyond what these checks measured.