Skip to main content
Glama

Related Servers

Alternatives to GuardBot

  • 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
    Check a token address before acting on a pool alert. VetAgent reports liquidity across eight chains. On Ethereum, BSC and Base, it reports available sell-simulation and tax evidence and whether the simulation matches the displayed pool. On Solana it checks token authorities and liquidity. An unavailable sell check is disclosed. Try one address over MCP or HTTP without an API key.
    3
    MIT

Related Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI assistants and trading agents to run Solana memecoin safety checks, including grades, red flags, launch bundles, same-second sellers, rug-farm links, and wallet activity.
    78 npm
    MIT
  • A
    license
    B
    quality
    D
    maintenance
    Provides on-chain forensic checks for evaluating transaction risks, including token verification, rug-pull detection, and fund tracing, using public blockchain endpoints.
    12
    39 npm
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Enables pre-flight 0x token and URL security audits, OFAC/sanctions wallet screening, DEX order-flow and due-diligence analysis, and executable EVM swap quotes via zero-config stdio or remote HTTP.
    5
    342 npm
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to screen ERC-20 tokens on Base and Ethereum for honeypot and rug-pull risks, including upgradeable proxies, owner powers, and trading restrictions, before swapping or approving. It also provides best swap route quotes with approval targets and unsigned transactions for the agent to sign and send.
    MIT

TDQS

A4.4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a distinct responsibility: check_approvals lists existing approvals, simulate_revoke tests a specific revocation, and check_token evaluates a token's safety. The workflow relationship between check_approvals and simulate_revoke is clearly separated by read vs. simulate.

Naming Consistency4/5

Names follow a clean verb_noun pattern, with check_approvals and check_token sharing the 'check' prefix. simulate_revoke is the only deviation, but the verb accurately reflects its action and is still in the same structural style.

Tool Count5/5

Three tools is well-scoped for a guard-focused server: inspect approvals, simulate a revoke, and vet a token before trading. Each tool covers a distinct user need with no redundancy or bloat.

Completeness4/5

The tool surface covers the core workflows: discovering risky approvals, proving a revoke works before signing, and detecting malicious tokens. A minor gap is the lack of any execution/broadcast capability, but the tools intentionally stop at simulation and calldata generation.

Maintenance

ActivitySlowing
ResponsivenessNo recent community issues