Remote MCP server that screens Base tokens for rug-pull liquidity, honeypots, copycats and owner powers, with an optional AI-written summary.
What you can do
Run a full risk report on a Base token, including an AI-written plain-English summary
Run a quick risk screen returning a 0-100 score, LOW/MEDIUM/HIGH level and per-check reasons
Check creator or launch wallet liquidity pull risk, including Uniswap V4
Check for copycat tickers, honeypot behavior and taxes
Check mint, pause and blacklist powers, upgradeable proxy, ownership and holder distribution
Identify the launch platform (Clanker, Doppler, B20)
When to use it
Useful when you want an assistant to vet a Base token before trading or interacting with it, or to compare several tokens quickly. The quick check suits fast screening; the full report suits a deeper read with a plain-English explanation.
Requirements
A remote streamable HTTP endpoint; no local install, package, environment variable or header is declared. Payment per call is handled through x402 in USDC, so a funded wallet or x402-capable client is implied.
Before you install
Calls are paid per use via x402 in USDC, so usage spends real funds. Results are automated risk signals, not investment advice, and a LOW score does not guarantee a token is safe. The token address you submit is sent to a third-party hosted service.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.DIMSUM1232011-svg%2Ftoken-risk-checker/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Full risk report for a Base token, with an AI-written plain-English summary: whether the creator or launch wallet can pull the pool liquidity (incl. Uniswap V4), copycat tickers, launch platform (Clanker/Doppler/B20), honeypot and taxes, mint/pause/blacklist powers, upgradeable proxy, ownership and holders. Returns a 0-100 score, LOW/MEDIUM/HIGH level and per-check reasons. Automated risk screen, not a security audit.
Parameterschainaddressrequired
quick_token_risk
Quick token risk check
Quick risk check for a Base token: the same checks as check_token_risk (creator-pullable liquidity, copycats, honeypot and taxes, owner powers, proxy, ownership, launch platform, holders) without the AI summary. Returns a 0-100 score, LOW/MEDIUM/HIGH level and per-check reasons. Automated risk screen, not a security audit.
Parameterschainaddressrequired
Version history
1
v1.0.0LatestOct 21, 2026
Score
83%
83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.