Remote MCP · Endpoint

io.github.Abstract36/stakechain MCP server

No. io.github.Abstract36/stakechain answered an MCP handshake 6 days ago.

UpLast checked 6 days ago

Server URL

https://stakechain-api.vercel.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.Abstract36/stakechain
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
111 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 9 checks
Described by its publisher as
Live Base staking/lending yields (APY, TVL, vaults) as MCP tools; x402 pay-per-request tier
Listing
From the official MCP registry (active).
Recent checks of io.github.Abstract36/stakechain
CheckedResultHandshake
6 days agoHandshake completed111 ms
7 days agoHandshake completed66 ms
7 days agoHandshake completed72 ms
9 days agoHandshake completed71 ms
10 days agoHandshake completed61 ms
11 days agoHandshake completed67 ms
12 days agoHandshake completed58 ms
13 days agoHandshake completed2.51 s
15 days agoHandshake completed71 ms

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

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