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
    39 npm
    MIT
  • A
    license
    A
    quality
    D
    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
    Not graded
    quality
    B
    maintenance
    Gives AI trading agents machine-readable trust and risk verdicts on Solana by checking whether a wallet's realized PnL makes it worth copying, where its funds came from, whether a token is structurally safe, and what a given trade size would really cost in slippage. Exposes these four checks as MCP tools callable against a hosted x402 pay-per-call API, so agents can hard-stop bad trades without RPC keys, signup, or local setup.
    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

ActivityMaintained
ResponsivenessNo issues