Skip to main content
Glama
zvmzaretsky

FabTally Decode MCP

by zvmzaretsky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to FabTally Decode MCP

No user-submitted related servers found.

    Related Servers

    • evm-recon-mcp

      franckyo
      A
      license
      A
      quality
      C
      maintenance
      Enables reading and analyzing deployed EVM smart contracts by fetching bytecode, disassembling with invalid jump detection, reading storage, deriving Solidity storage slots, and decoding calldata on any EVM chain without an API key.
      8
      MIT

    • calldata-guardian

      Baneado98
      A
      license
      A
      quality
      C
      maintenance
      Decodes Ethereum calldata and returns a safety verdict with plain-English explanations of what the transaction does, flagging dangerous actions like unlimited approvals or gasless permits.
      2
      MIT

    • jwt-decoder

      Br0ski777
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to decode and inspect JWT tokens without signature verification, extracting header, payload, claims, expiry, and signing algorithm while handling payment via the x402 micropayment protocol.
      MIT

    • singularity

      DarkStarMatters
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying blockchains across EVM, Solana, Bitcoin/UTXO, and Cosmos through a unified interface, with tools for resolving addresses, checking balances, fetching transactions and blocks, reading contracts, decoding calldata, and building unsigned transfers.
      42 npm
      3
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct operation: log decoding, calldata decoding, selector/topic resolution, and ABI fetching. The inputs and outputs are clearly differentiated, so an agent would have no trouble selecting the right tool for a given task.

    Naming Consistency4/5

    All tool names use lowercase snake_case, but the verb/noun order is inconsistent: decode_log and decode_calldata are verb_noun, while selector_lookup and abi_fetch are noun_verb. This is a minor deviation from a uniform pattern, but the names still read predictably.

    Tool Count5/5

    With 4 tools, the server is well-scoped for its purpose of decoding EVM data. Each tool covers a distinct aspect of the decoding workflow, and there is no redundancy or bloat.

    Completeness5/5

    The tool set covers the full decoding lifecycle: fetching ABIs, resolving selectors/topics, decoding calldata, and decoding event logs. There are no obvious gaps for typical EVM decoding tasks, and the tools work together as a complete pipeline.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources