Token Safety & Contract Risk API
Let your coding agent screen ERC-20-style token contracts for honeypots, taxes, proxies, and blacklist risk before you wire on-chain payments into a product.
Overview
io.github.Br0ski777/token-safety is an MCP server for the Validate phase that checks token contracts for honeypot, tax, proxy, blacklist, and GoPlus-backed risk scores.
What is this MCP server?
- GoPlus-powered checks: honeypot flags, buy/sell tax, proxy patterns, and blacklist signals
- Aggregated contract risk score for quick agent-side triage
- Remote MCP over SSE at token-safety.api.klymax402.com (server schema v2025-12-11)
- x402 micropayment model for pay-per safety lookup
- Version 1.1.0 published from Br0ski777/token-safety-x402 on GitHub
- Server version 1.1.0
- Remote transport: SSE at https://token-safety.api.klymax402.com/mcp
- Risk dimensions cited: honeypot, tax, proxy, blacklist, composite risk score (GoPlus-powered)
What problem does it solve?
You cannot tell from marketing copy whether a token contract will trap users with honeypots, extreme taxes, or hidden proxies.
Who is it for?
Indie builders validating crypto payments, token gates, or on-chain features who want agent-callable contract risk checks without standing up GoPlus clients themselves.
Skip if: Teams that need formal security audits, legal compliance sign-off, or deep bytecode review without any on-chain or micropayment setup.
What do I get? / Deliverables
Your agent returns structured safety signals and a risk score so you can reject bad tokens or document assumptions before writing integration code.
- Structured token safety assessment (honeypot, tax, proxy, blacklist, risk score)
- Agent-readable JSON suitable for scope notes or integration guardrails
Recommended MCP Servers
Journey fit
Token contract checks belong in Validate when you are scoping crypto, marketplace, or x402 integrations and need go/no-go signals before Build. Scope is where solo builders decide whether a chain or token model is safe enough to commit engineering time; this MCP surfaces GoPlus-style risk scores at that gate.
How it compares
Remote GoPlus-style contract screening over MCP, not a local agent skill or a full pentest engagement.
Common Questions / FAQ
Who is io.github.Br0ski777/token-safety for?
Solo and indie builders using AI coding agents who need quick token contract risk checks while scoping Web3 or x402 product ideas.
When should I use io.github.Br0ski777/token-safety?
Use it during Validate before you commit to integrating a specific token or chain, or when reviewing user-supplied contract addresses in agent workflows.
How do I add io.github.Br0ski777/token-safety to my agent?
Register the remote MCP server (SSE URL https://token-safety.api.klymax402.com/mcp) in Claude Code, Cursor, or another MCP-capable client per your editor’s remote-server docs, and ensure x402 payment is configured if required by the host.