Token Safety & Contract Risk API
Token safety check — honeypot, tax, proxy, blacklist, risk score. GoPlus-powered. x402.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport sse token-safety-contract-risk-api 'https://token-safety.api.klymax402.com/mcp'
{
"mcpServers": {
"token-safety-contract-risk-api": {
"type": "sse",
"url": "https://token-safety.api.klymax402.com/mcp"
}
}
}
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
Token Safety & Contract Risk API
Token contract safety scanner -- honeypot, tax, proxy, blacklist, ownership. Rug-pull protection for agents. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.
Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.
Quickstart -- MCP
Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):
{
"mcpServers": {
"token-safety": {
"url": "https://token-safety.api.klymax402.com/mcp"
}
}
}
Quickstart -- HTTP (x402)
curl "https://token-safety.api.klymax402.com/api/check?address=0x0000000000000000000000000000000000dEaD"
# -> 402 Payment Required, with an x402 payment challenge in the response body
Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.
Tools
| Tool | Method | Path | Price | Description |
|---|---|---|---|---|
token_check_safety | GET | /api/check | $0.008 | Check token contract safety and risk score |
token_check_safety
Use this when you need to check if a token is safe before buying or interacting with it. Returns a comprehensive safety report in JSON.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
address | string | yes | Token contract address (e.g. 0x...) |
chain | string | no | Chain to check on: 'ethereum' or 'base' (default: ethereum) |
Returns
isHoneypot-- whether the token traps buyers (cannot sell)ownershipRenounced-- whether the contract owner has renounced controlisProxy-- whether the contract is upgradeable (proxy risk)buyTax-- percentage tax on buy transactionssellTax-- percentage tax on sell transactionsmaxTxPercent-- maximum transaction size as percent of supplyliquidityLocked-- whether liquidity is lockedhasBlacklist-- whether contract has a blacklist functionholderCount-- total number of token holdersriskScore-- overall risk score (0=safe, 100=dangerous)
Example response:
{"isHoneypot":false,"ownershipRenounced":true,"isProxy":false,"buyTax":0,"sellTax":0,"maxTxPercent":100,"liquidityLocked":true,"hasBlacklist":false,"holderCount":15420,"riskScore":12}
When to use: buying any new or unknown token. Essential for rug-pull protection and due diligence.
Not for: token prices (use dex_get_swap_quote), wallet balance (use wallet_get_portfolio), holder distribution (use token_get_holder_analysis).
Example agent prompts
- "Check if a token is safe before buying or interacting with it"
Payment
- Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
- Network: Base L2 (
eip155:8453) - Asset: USDC
- Facilitator: Coinbase CDP (primary), PayAI (fallback)
- Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)
Part of klymax402
100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.
- Catalog: https://klymax402.com/llms.txt
- Full API reference: https://klymax402.com/llms-full.txt
- Live stats: https://klymax402.com/stats
License
MIT
Frequently asked questions
What is Token Safety & Contract Risk API?
Token safety check — honeypot, tax, proxy, blacklist, risk score. GoPlus-powered. x402.
How do I install Token Safety & Contract Risk API?
It runs as a remote server. In Claude Code: claude mcp add --transport sse token-safety-contract-risk-api 'https://token-safety.api.klymax402.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Token Safety & Contract Risk API need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is Token Safety & Contract Risk API open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains Token Safety & Contract Risk API?
It is published by Br0ski777. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.