FabTally Decode

Name: FabTally Decode
Author: zvmzaretsky

MCP serverMCP

Decode EVM bytes to JSON: event-log decoder, calldata explainer, selector lookup, ABI fetch.

by zvmzaretskyrepository ↗homepage ↗v1.0.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"fabtally-decode","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability109/109 checks ok

when	check	result	http	latency	detail
4 h ago	mcp initialize	ok	200	9 ms	server fabtally-decode 1.0.0 · protocol 2025-06-18 · 4 tools
11 h ago	mcp initialize	ok	200	10 ms	server fabtally-decode 1.0.0 · protocol 2025-06-18 · 4 tools
18 h ago	mcp initialize	ok	200	16 ms	server fabtally-decode 1.0.0 · protocol 2025-06-18 · 4 tools
24 h ago	mcp initialize	ok	200	17 ms	server fabtally-decode 1.0.0 · protocol 2025-06-18 · 4 tools
31 h ago	mcp initialize	ok	200	16 ms	server fabtally-decode 1.0.0 · protocol 2025-06-18 · 4 tools
2 d ago	mcp initialize	ok	200	19 ms	server fabtally-decode 1.0.0 · protocol 2025-06-18 · 4 tools
2 d ago	mcp initialize	ok	200	34 ms	server fabtally-decode 1.0.0 · protocol 2025-06-18 · 4 tools
2 d ago	mcp initialize	ok	200	16 ms	server fabtally-decode 1.0.0 · protocol 2025-06-18 · 4 tools
2 d ago	mcp initialize	ok	200	17 ms	server fabtally-decode 1.0.0 · protocol 2025-06-18 · 4 tools
3 d ago	mcp initialize	ok	200	15 ms	server fabtally-decode 1.0.0 · protocol 2025-06-18 · 4 tools

Tools observed via MCP handshake

decode_log — PAID $0.003 (x402, USDC on Base). FLAGSHIP: decode EVM event LOGS to human-readable JSON. Give {chain, tx_hash} to decode every log in a transaction, OR {chain,
decode_calldata — PAID $0.002 (x402, USDC on Base). Decode a contract function call. Give {chain, to?, data, abi?}; get the 4-byte selector resolved to a function signature (via
selector_lookup — PAID $0.001 (x402, USDC on Base). Resolve a 4-byte function selector (0x + 8 hex) OR a 32-byte event topic hash (0x + 64 hex) to its human-readable signature(s)
abi_fetch — PAID $0.002 (x402, USDC on Base). Fetch the verified ABI + metadata for a contract. Give {address, chain}; get the ABI JSON, verification status/source (Sourcif

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.github.zvmzaretsky/onchain-decode

first seen 1 mo ago · fetched 33 h agoopen ↗

Field history (7 recent events)

1 mo ago · declared · summary → "Decode EVM bytes to JSON: event-log decoder, calldata explainer, selector lookup, ABI fetch."
1 mo ago · declared · description → "Decode EVM bytes to JSON: event-log decoder, calldata explainer, selector lookup, ABI fetch."
1 mo ago · declared · publisherName → "zvmzaretsky"
1 mo ago · declared · homepageUrl → "https://decode.fabtally.com"
1 mo ago · declared · repoUrl → "https://github.com/zvmzaretsky/onchain-decode-mcp"
1 mo ago · declared · version → "1.0.0"
1 mo ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from