Skip to main content
Glama

Check token safety (honeypot / rug risk)

check_token
Read-onlyIdempotent

Check whether a crypto token is safe to buy, hold or sell before trading it. Works on 45 chains: Ethereum, BNB Chain, Base, Arbitrum, Polygon, Optimism, Avalanche and other EVM chains, plus Solana, Tron and Sui. Detects honeypots (live sell simulation on Ethereum, BNB Chain, Base), buy/sell tax, owner powers (mint, pause, blacklist, change tax, hidden owner), Solana mint/freeze authority and Token-2022 traps, proxy/upgradeable contracts, LP lock, top-holder concentration, source verification and age. Returns verdict SAFE, CAUTION or DANGER, a 0-100 score, and plain-English reasons citing GoPlus, honeypot.is, RugCheck or on-chain RPC. Free: 3 checks per day per IP; when used up, the result explains the paid x402 endpoint instead. Not financial advice.

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": {
      "token": "<token>"
    },
    "name": "check_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoChain key from list_chains (aliases and EVM chain ids like '1' or '8453' also work). Defaults to bsc for 0x addresses; Solana, Tron and Sui addresses are auto-detected if omitted.bsc
tokenYesToken contract address: 0x… (EVM), base58 mint (Solana), T… (Tron) or coin type 0x…::module::NAME (Sui).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, and the description adds substantial context on top: what is actually detected per chain (live honeypot sell simulation only on Ethereum/BNB/Base, Solana mint/freeze authority, Token-2022 traps), the verdict/score/reason response shape, cited data sources, and the free-tier quota and paid fallback behavior.

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?

The purpose and scope are front-loaded in the first sentence, followed in a logical order by chains, detections, return values, quota mechanics and disclaimer. It is dense and nearly every clause carries information, though the chain roster plus the detection list makes it longer than strictly necessary for an agent.

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

Completeness5/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 still specifies the return contract (SAFE/CAUTION/DANGER verdict, 0-100 score, plain-English reasoning with source attribution) and the quota-exhaustion behavior. Combined with per-chain detection caveats, an agent has enough to call it correctly and interpret results.

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 description coverage is 100%, so the schema already documents the chain enum, the bsc default, EVM chain-id aliases, and auto-detection for Solana/Tron/Sui, and the token address formats. The description reinforces chain breadth ('45 chains') but adds no syntax or format detail beyond the structured fields, so the 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?

The description opens with a concrete verb and resource ('Check whether a crypto token is safe to buy, hold or sell'), names the decision it supports (pre-trade), and enumerates the specific detections and verdict outputs. An agent can distinguish this from the only sibling, list_chains, without opening any schema.

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?

It states a clear usage condition — run before trading a token — and notes the operational constraint of 3 free checks per day per IP with x402 as the paid fallback, which shapes when an agent should call it. It does not name an explicit alternative tool or state when not to use it, so it falls short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources