What it does
The token_check_safety tool takes a token contract address and an optional chain, either ethereum or base, with ethereum as the default. It returns a JSON safety report covering whether the token traps buyers, whether ownership has been renounced, whether the contract is upgradeable, buy and sell tax percentages, maximum transaction size as a share of supply, whether liquidity is locked, whether a blacklist function exists, the holder count, and an overall risk score where 0 is safe and 100 is dangerous.
It is meant for checking a token before buying it or interacting with it. Token prices, wallet balances and holder distribution are outside its scope and are covered by other tools.
Each call is paid per request in USDC on Base through the x402 protocol, with no API key or signup. An x402-aware client handles the payment challenge, signing and retry. The server is added to an MCP client configuration such as Claude Desktop, Cursor or ElizaOS.
Limitations and requirements
Each call requires an x402-aware client and a wallet that can sign USDC payments on Base. Chain checks are limited to ethereum and base.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
Token Safety & Contract Risk API
Token safety check — honeypot, tax, proxy, blacklist, risk score. GoPlus-powered. x402.
v1.1.0As shown on registry.modelcontextprotocol.io when we last read it