Remote MCP · Endpoint
FabTally Decode MCP server
No. FabTally Decode answered an MCP handshake 5 hours ago.
UpLast checked 5 hours ago
Server URL
https://decode.fabtally.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.zvmzaretsky/onchain-decode
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 284 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Decode EVM bytes to JSON: event-log decoder, calldata explainer, selector lookup, ABI fetch.
- Website
- https://decode.fabtally.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 5 hours ago | Handshake completed | 284 ms |
| 2 days ago | Handshake completed | 485 ms |
| 4 days ago | Handshake completed | 309 ms |
| 5 days ago | Handshake completed | 280 ms |
| 7 days ago | Handshake completed | 284 ms |
| 8 days ago | Handshake completed | 282 ms |
| 9 days ago | Handshake completed | 280 ms |
| 12 days ago | Handshake completed | 266 ms |
| 13 days ago | Handshake completed | 279 ms |
| 15 days ago | Handshake completed | 280 ms |
| 16 days ago | Handshake completed | 277 ms |
| 17 days ago | Handshake completed | 278 ms |
| 18 days ago | Handshake completed | 282 ms |
| 19 days ago | Handshake completed | 288 ms |
| 20 days ago | Handshake completed | 276 ms |
| 21 days ago | Handshake completed | 294 ms |
| 22 days ago | Handshake completed | 280 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 FabTally Decode and makes no claim about it beyond what these checks measured.