Skip to main content
Glama
jakegu1

VetAgent

by jakegu1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to VetAgent

No user-submitted related servers found.

    Related Servers

    • safeagent-token-safety

      Aigen-Protocol
      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

    • token-safety

      Br0ski777
      A
      license
      Not graded
      quality
      B
      maintenance
      Checks token contract safety for honeypot, tax, proxy, blacklist, ownership risks, and returns a risk score, enabling rug-pull protection for agents via pay-per-call x402 micropayments.
      MIT
    • AgentRisk MCP by Neurobyteio

      AgentRisk MCPofficial

      Neurobyteio
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents on Base to call a check_token_risk tool before trading, providing honeypot detection, LP-lock verification, brand impersonation checks, and live sell simulation across Uniswap V2/V3/V4 and Aerodrome with a clear risk score and should-trade decision.
      1
      9 npm
      MIT

    • GuardBot

      anthonygozzini
      A
      license
      A
      quality
      A
      maintenance
      Pre-trade safety for EVM, Solana and TRON: simulates a real buy and a real sell against live liquidity, so a honeypot shows as a sell that fails instead of a vendor score, and audits a wallet's standing approvals across the three chains. Python standard library only, no API key.
      5
      3
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.5/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct stage in the token-vetting workflow: discovery of new pools, risk assessment, and liquidity snapshot. Although assess_token_risk and get_token_liquidity both touch liquidity, their purposes and outputs are clearly separated (verdict vs. market data).

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern: find_new_hot_pools, assess_token_risk, get_token_liquidity. The verbs are descriptive and the object nouns clearly identify the target resource.

    Tool Count5/5

    Three tools is well-scoped for a focused vetting agent: one discovery entry point, one risk-check entry point, and one liquidity-data entry point. No tool is redundant and none is missing from the core workflow.

    Completeness4/5

    The set covers the full discovery-to-risk-to-liquidity pipeline with no dead ends. Minor gaps exist, such as no historical-tracking or token-profile/summary tool beyond the risk check, but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources