FabTally Decode is answering right now. Last checked 2 min ago. It exposes 4 tools. Last commit 1 Aug 2026.
Decode EVM bytes to JSON: event-log decoder, calldata explainer, selector lookup, ABI fetch.
Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.
claude mcp add onchain-decode --transport http https://decode.fabtally.com/mcp
{
"mcpServers": {
"onchain-decode": {
"url": "https://decode.fabtally.com/mcp"
}
}
}
[mcp_servers.onchain-decode]
url = "https://decode.fabtally.com/mcp"
{
"mcpServers": {
"onchain-decode": {
"url": "https://decode.fabtally.com/mcp"
}
}
}
{
"mcpServers": {
"onchain-decode": {
"url": "https://decode.fabtally.com/mcp"
}
}
}
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
decode_calldata
decode_log
abi_fetch
selector_lookup
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://decode.fabtally.com/mcp | streamable-http | answering | 107 ms | 2 min ago |
Webhook Ai tools for AI agents. Capabilities: validate webhook signature, log webhook event, replay
Tickory MCP server for Binance scans, alert events, and explainability.
Browser + dev-server logs on one correlated timeline, for Claude Code and AI agents.
Docker for AI agents — containers, compose stacks, logs and databases, locally or over SSH.
Web cron for sites without their own scheduler: calls your URLs on schedule and logs every call.
Timer and time-tracking add-on: start/stop timers, log entries, CSV export. Data stays local.
Pre-execution gate for AI-agent tool calls. Touch ID approval. Tamper-evident audit log.
MCP server exposing rlg log streams to LLM agents via JSON-RPC 2.0 over stdio.
Answers built from our own checks of this server.