Skip to main content
Glama

Related Servers

Alternatives to GuardBot

  • A
    license
    Not graded
    quality
    C
    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
    Pre-trade token safety check for AI agents. Simulates a sell before you buy, then reports honeypot, tax, liquidity, pair age, same-ticker impersonation and owner powers as one low/medium/high/unknown verdict. Fail-closed: when a critical check cannot run it answers unknown rather than guessing low. Publishes its own measured error rate with the benchmark harness in the repo.
    3
    MIT

Related Servers

  • A
    license
    B
    quality
    B
    maintenance
    Provides on-chain forensic checks for evaluating transaction risks, including token verification, rug-pull detection, and fund tracing, using public blockchain endpoints.
    12
    16 npm
    MIT
  • A
    license
    A
    quality
    C
    maintenance
    Per-transaction crypto trade validator for AI agents, validates trades with PROCEED/CAUTION/BLOCK verdicts, scans tokens for anomalies, detects rug pulls, and searches across DEXes. Powered by WaveGuard physics engine with deterministic PDE-based analysis.
    5
    1
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    On-chain Solana token safety for trading agents — traces coordinated wallet funding, same-block Jito bundles, serial-rug deployers and live coordinated dumps into one Exit-Liquidity Risk verdict before a swap. Free tier, then $0.02 USDC/query via x402.
    1
    18 npm
    1
    MIT

TDQS

A4.2/5.0

Scored across 2 tools

Disambiguation5/5

check_token evaluates a token's tradability and impersonation risk, while check_approvals audits a wallet's existing allowances across chains. They target different objects and perform different kinds of safety analysis, so an agent cannot confuse them.

Naming Consistency5/5

Both tools follow the same verb_noun pattern: check_token and check_approvals. This is a clear, consistent convention with no mixed naming styles or vague verbs.

Tool Count3/5

Only two tools feels thin for a general-purpose security bot, but the tools are tightly scoped to token safety and wallet approval checks. The count is defensible but still sits on the borderline where a small set may feel sparse.

Completeness4/5

The core domain is covered well: token buy/sell simulation, honeypot and tax detection, ticker impersonation, and multi-chain approval discovery are all present. Missing features like revocation or deeper transaction simulation are not clearly promised, so the gap is minor rather than severe.

Maintenance

ActivityMaintained
ResponsivenessNo issues