Skip to main content
Glama
crypto-inspector-mcp

crypto-inspector-mcp

by rabbit385

Related Servers

Alternatives to crypto-inspector-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      F
      maintenance
      Enables AI agents to scan crypto tokens for rug pulls, scams, and risk using a six-agent consensus system. It provides real-time security audits and risk scoring for tokens on Solana, Ethereum, Base, and BSC.
      6
      33 PyPI
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Token safety oracle for AI agents. Honeypot detection, 17 scam pattern checks, LP lock verification across 6 EVM chains. Score 0-100 with risk flags. ERC Token Safety Score standard.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to assess the risk of crypto wallets, tokens, and smart contracts by providing read-only on-chain analysis, 0-100 risk scoring with explanations, fund tracing, and contract inspection before interaction.
      6
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to check whether a crypto token, link, or forwarded "gem" message is a scam by running contract rules, live test trades, creator history, and market data across 64 networks, returning plain-English or Pidgin verdicts. Also supports scanning messages, reviewing a token's past checks, and explaining individual findings.
      5
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Real-time smart contract security for autonomous AI agents, offering tools for contract verification, wallet monitoring, drain detection, threat reporting, and leaderboards.
      19
      25 npm
      MIT

    TDQS

    B3.2/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusing it with another. The single inspect_token tool has a clearly defined purpose, so an agent cannot misselect it.

    Naming Consistency4/5

    The only tool name follows a clear verb_noun convention (inspect_token) and accurately reflects its function. There is no set of tools to establish a broader naming pattern, but the name is well-formed and self-explanatory.

    Tool Count2/5

    The server exposes only one tool for what is described as a comprehensive security and liquidity check. This feels too thin for the as a token inspection MCP, which would typically benefit from separately callable tools for specific aspects such as liquidity details, holder analysis, or price data.

    Completeness2/5

    The tool surface is extremely limited, offering only a single monolithic action. While the description claims a comprehensive check, there are no additional tools for focused queries, comparing tokens, or retrieving specific aspects of the analysis, leaving obvious gaps in an inspection workflow.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues