Token Safety & Contract Risk API

Registre officiel Finance et paiements

Token safety check — honeypot, tax, proxy, blacklist, risk score. GoPlus-powered. x402.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (sse)
Claude Code
claude mcp add --transport sse token-safety-contract-risk-api 'https://token-safety.api.klymax402.com/mcp'
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "token-safety-contract-risk-api": {
            "type": "sse",
            "url": "https://token-safety.api.klymax402.com/mcp"
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. Token Safety & Contract Risk API
  2. Quickstart -- MCP
  3. Quickstart -- HTTP (x402)
  4. Tools
  5. Example agent prompts
  6. Payment
  7. Part of klymax402
  8. License

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

ToolMethodPathPriceDescription
token_check_safetyGET/api/check$0.008Check 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

NameTypeRequiredDescription
addressstringyesToken contract address (e.g. 0x...)
chainstringnoChain to check on: 'ethereum' or 'base' (default: ethereum)

Returns

  • isHoneypot -- whether the token traps buyers (cannot sell)
  • ownershipRenounced -- whether the contract owner has renounced control
  • isProxy -- whether the contract is upgradeable (proxy risk)
  • buyTax -- percentage tax on buy transactions
  • sellTax -- percentage tax on sell transactions
  • maxTxPercent -- maximum transaction size as percent of supply
  • liquidityLocked -- whether liquidity is locked
  • hasBlacklist -- whether contract has a blacklist function
  • holderCount -- total number of token holders
  • riskScore -- 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.

License

MIT

Questions fréquentes

Qu'est-ce que Token Safety & Contract Risk API ?

Token safety check — honeypot, tax, proxy, blacklist, risk score. GoPlus-powered. x402.

Comment installer Token Safety & Contract Risk API ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport sse token-safety-contract-risk-api 'https://token-safety.api.klymax402.com/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour Token Safety & Contract Risk API ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

Token Safety & Contract Risk API est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient Token Safety & Contract Risk API ?

Il est publié par Br0ski777. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.