Skip to main content
Glama
ossamartinaaron09-ui

Base Contract Auditor MCP Server

by ossamartinaaron09-ui
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Base Contract Auditor MCP Server

No user-submitted related servers found.

    Related Servers

    • verdix by verdixapi

      verdixofficial

      verdixapi
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to check an EVM address on Base for risk (safe, caution, danger) before sending funds, with reasons, paid per call via x402 from the user's own wallet.
      6
      51 npm
      MIT

    • aegis-x402-mcp

      Goatincrypto
      A
      license
      A
      quality
      C
      maintenance
      Enables AI coding assistants and trading bots to verify smart contracts, test honeypot traps, assess DEX liquidity, and check wallet counterparty risk before deploying or trading capital on Base. It exposes preflight clearance, token audits, KYA reputation, and web-scraping tools with free and paid x402 tiers.
      7
      524 npm
      MIT

    • Base Pulse

      Timothymycompc
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to run honeypot and owner-power safety checks on Base tokens and to read wallet ETH and USDC balances, with every answer sourced from real chain data and paid per call in USDC via x402.
      MIT

    • pyresec

      renaat-s
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible agents to submit source code for automated SAST/SCA security audits paid via x402 USDC micropayments on Base, returning structured vulnerability findings, CWE IDs, and optional remediated code patches.
      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/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: performing the audit, fetching payment parameters for it, and checking gateway health/version. The payment-info tool is prerequisite scaffolding for audit_contract, but its purpose is unambiguous and unlikely to be misselected.

    Naming Consistency5/5

    All three follow a clean verb_noun pattern (audit_contract, get_payment_info, check_service_status) with consistent snake_case. No mixing of conventions.

    Tool Count5/5

    Three tools is the minimum for this niche x402-paid audit workflow, and each earns its place: discover payment details, execute the audit, verify service health. Nothing superfluous.

    Completeness3/5

    The core flow (get payment info → audit_contract) is covered, but there is no tool to check payment confirmation, retrieve prior audit results/history, or verify a specific audit by ID. Agents hitting a failed or pending payment have limited recovery paths.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources