Remote MCP · Endpoint

web3ctx MCP server

No. web3ctx answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.scarai.xyz/mcp

The last check completed an MCP handshake.

Registry name
io.github.FarseenSh/web3ctx
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
243 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Version-true web3 docs, ABIs and human-validated integration recipes over MCP.
Listing
From the official MCP registry (active).
Recent checks of web3ctx
CheckedResultHandshake
2 hours agoHandshake completed243 ms
2 days agoHandshake completed507 ms
4 days agoHandshake completed194 ms
5 days agoHandshake completed182 ms
7 days agoHandshake completed194 ms
8 days agoHandshake completed477 ms
9 days agoHandshake completed187 ms
12 days agoHandshake completed176 ms
13 days agoHandshake completed43 ms
15 days agoHandshake completed197 ms
17 days agoHandshake completed241 ms
18 days agoHandshake completed168 ms
19 days agoHandshake completed263 ms
20 days agoHandshake completed151 ms
20 days agoHandshake completed155 ms
21 days agoHandshake completed190 ms
22 days agoHandshake completed72 ms

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

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