Skip to main content
Glama
devx-address-poisoning-check

devx-address-poisoning-check

Related Servers

Alternatives to devx-address-poisoning-check

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to check a payment recipient against the sender's own on-chain history before funds move, flagging address-poisoning look-alikes, spoofed 'from you' transfers, and fake tokens via the Blockscout PRO API. It also scans a wallet for poisoning attempts aimed at it, returning a verdict of OK, CAUTION, or STOP.
      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
      Not graded
      quality
      B
      maintenance
      Enables AI agents to trace Ethereum transactions and addresses, check recipients before payment, and run wallet checkups for risky approvals, returning route evidence as plain text and JSON.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to run pre-sign risk checks on transactions, approvals, EIP-712 signatures, token addresses, wallet approvals, sanctions screening, and prompt-injection texts, returning green/orange/red verdicts with machine-readable reason codes before signing.
      1
      AGPL 3.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to perform pay-per-call security verification of wallets, tokens, contracts, dApps, agents, and more via a remote endpoint with no installation.
      2
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-compatible AI agents to scan crypto transactions for scam addresses, clipboard-hijack patterns, and typos, as well as report scam addresses and check usage, directly in conversation.
      -

    TDQS

    A4.5/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly separate roles: one performs the offline lookalike/checksum check, while the other only returns metadata about an optional paid on-chain service. Their names and descriptions make it hard to confuse the action tool with the informational tool.

    Naming Consistency4/5

    Both names use snake_case and are descriptive, but they do not follow a uniform verb_noun pattern: check_recipient_lookalike is action-oriented, while onchain_check_info is an info getter. This is a minor deviation rather than inconsistent style.

    Tool Count3/5

    Only two tools are provided, which feels thin even for a narrow pre-transfer address-checking server. The count is defensible because one tool does the main check and the other explains an optional paid alternative, but the surface is borderline minimal.

    Completeness3/5

    The core offline lookalike and checksum check is covered, but the on-chain history scan is not exposed as a callable tool, only as endpoint metadata. That is a notable gap for a server framed around address-poisoning detection, requiring an external paid workflow to complete the lifecycle.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data