Skip to main content
Glama

Related Servers

Alternatives to Web3 EVM Debugger & Auditor MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to audit Solidity smart contracts for security vulnerabilities, fetch verified source code from block explorers, decode calldata, and estimate gas costs across major EVM networks.
      4
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables automated Solidity smart contract auditing by analyzing callgraphs and control flow to detect reentrancy vulnerabilities. Integrates with MCP-compatible clients to provide deterministic, zero-dependency security assessments.
      8
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables static security audit of Solidity smart contracts by analyzing source code or deployed bytecode for vulnerabilities, providing risk scores and detailed findings.
      1
      MIT
    • A
      license
      A
      quality
      B
      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
      462 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides tools for querying onchain data across 12+ blockchain networks, including token balances, transaction analysis, and smart contract security auditing. It enables users to interact with multiple EVM-compatible chains and perform deep contract evaluations through natural language interfaces.
      1
      -

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a clearly distinct task in EVM debugging/auditing, such as Yul sanitization, reentrancy analysis, trace debugging, calldata decoding, storage layout calculation, and EIP-1271 verification. There is no overlap in purpose, so an agent can easily select the correct tool.

    Naming Consistency4/5

    All tool names use snake_case and are descriptive, but the pattern is predominantly noun-based (e.g., _sanitizer, _verifier, _debugger, _auditor, _calculator) with one verb-first name (decode_evm_calldata). This is a minor deviation from a uniform verb_noun convention, though still readable and predictable.

    Tool Count5/5

    Six tools is well-scoped for a specialized EVM debugging and auditing server. Each tool addresses a unique concern without redundancy, and the count falls comfortably within the ideal 3–15 range.

    Completeness4/5

    The surface covers core auditing and debugging tasks such as reentrancy detection, Yul bug scanning, storage layout calculation, calldata decoding, trace debugging, and EIP-1271 signature verification. However, it lacks coverage for EOA signature verification, event log decoding, and bytecode disassembly, which are common ancillary needs in this domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues