Remote MCP · Endpoint
web3ctx MCP server
No. web3ctx answered an MCP handshake 1 hour ago.
UpLast checked 1 hour 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
- 177 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Version-true web3 docs, ABIs and human-validated integration recipes over MCP.
- Website
- https://web3ctx.scarai.xyz/
- Repository
- https://github.com/FarseenSh/web3ctx
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 177 ms |
| 1 day ago | Handshake completed | 217 ms |
| 2 days ago | Handshake completed | 193 ms |
| 3 days ago | Handshake completed | 188 ms |
| 4 days ago | Handshake completed | 343 ms |
| 5 days ago | Handshake completed | 170 ms |
| 6 days ago | Handshake completed | 456 ms |
| 9 days ago | Handshake completed | 349 ms |
| 11 days ago | Handshake completed | 366 ms |
| 14 days ago | Handshake completed | 372 ms |
| 16 days ago | Handshake completed | 339 ms |
| 18 days ago | Handshake completed | 191 ms |
| 20 days ago | Handshake completed | 243 ms |
| 22 days ago | Handshake completed | 507 ms |
| 24 days ago | Handshake completed | 194 ms |
| 26 days ago | Handshake completed | 182 ms |
| 27 days ago | Handshake completed | 194 ms |
| 29 days ago | Handshake completed | 477 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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.