Skip to main content
Glama

Check Token Smart Contract Security & Honeypot Status

check_token_security
Read-onlyIdempotent

Audit a token contract for honeypots, buy/sell taxes, mint authority, blacklists, and balance backdoors before trading. Supports Base, Ethereum, Solana, BSC, Arbitrum, and Polygon.

Instructions

Performs a fast, fail-closed smart contract security and anti-honeypot audit via GoPlus on Base, Solana, Ethereum, BSC, Arbitrum, or Polygon. Detects honeypots, buy/sell taxes (in % and basis points), balance modification backdoors, mint authority, and blacklists. Free to start with zero wallet or setup required (3 free queries/day); unlimited calls supported via optional Base prepaid session.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>"
    },
    "name": "check_token_security"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesThe token smart contract address (0x... for EVM chains like Base/Ethereum, or Base58 mint address for Solana). Example Base BRETT address: "0x532f27101965dd16442e59d40670faf5ebb142e4".
networkNoTarget blockchain network to audit: "base", "solana", "ethereum", "bsc", "arbitrum", or "polygon". Defaults to "base".base
paymentProofNoOptional Base USDC transaction hash ("0x...") for high-frequency trading bots needing unlimited calls. Leave empty for automatic free daily queries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.7.1
    • changedInput schema / properties / paymentProof / description
      Previous value: -"Optional Base USDC transaction hash (\"0x...\") or HTTP 402 payment header for unlimited calls after your 3 free daily queries. Deposit $1.00 USDC once on Base to 0x8a8c238ed2b46908Ff6C6922a3870984f20f8913 for 200 instant security audits."New value: +"Optional Base USDC transaction hash (\"0x...\") for high-frequency trading bots needing unlimited calls. Leave empty for automatic free daily queries."
  2. Addedv1.6.0

TDQS

A4.3/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds substantial context beyond the annotations: GoPlus as the backend, fail-closed semantics, the specific threat classes detected, and the quota model (3 free queries/day, unlimited via a Base prepaid session). That quota and fail-closed behavior are things the readOnly/idempotent annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core capability, then chains and quota details. Two dense sentences with little waste, though the promotional phrasing ('Free to start with zero wallet or setup required') is slightly padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description enumerates the key findings (honeypot verdict, buy/sell tax, mint authority, blacklists) so an agent knows what to expect. It does not describe the response structure or what 'fail-closed' returns on error, which leaves a small gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with enums and per-parameter descriptions already explaining address formats, network values and paymentProof. The description mainly restates the chain list and free-vs-paid model, adding little syntax or meaning the schema lacks, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource (security and anti-honeypot audit of a token contract) plus the data provider and supported chains. Clearly distinct from the sibling alpha/market-discovery tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context: use it to check a token for honeypots, taxes and backdoors before trading, with a note on the free tier and an optional paid path for high-frequency bots. It does not name a sibling alternative or state when not to use, which keeps it below 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.