
Ton Jetton Risk Mcp
io.github.mrvlyouknowwhoPublished by GitHub account mrvlyouknowwhov0.2.0Updated Oct 24, 2026
Token rug/honeypot risk screening: EVM (7 chains, live sell simulation), Solana, TON. Free, keyless.
Overview
A local MCP server that lets an assistant screen EVM, Solana and TON tokens for rug-pull and honeypot risk, returning a 0–100 score with flags and raw facts.
- What you can do
- Screen EVM tokens across seven chains for honeypot behaviour, including live buy/sell simulation, taxes, owner powers, proxy status, liquidity and holder concentration. Screen Solana tokens for mint and freeze authority, mutable balances, transfer hooks and fees, DEX liquidity and holder concentration. Screen TON jettons for unrevoked mint authority, admin presence, holder concentration, DEX liquidity and blacklist status, taxable transfers and honeypot heuristics. Return a 0–100 risk score with concrete flags and structured JSON facts for each assessment.
- When to use it
- Useful when an assistant is asked whether a specific token is safe to buy or trade, or when comparing risk across tokens on Ethereum, BSC, Base, Arbitrum, Polygon, Optimism, Avalanche, Solana or TON before acting.
- Requirements
- Runs as a local process, started with npx from the GitHub repository; no global install. Needs network access to GoPlus, honeypot.is, TonAPI and STON.fi. No API keys required; an optional TONAPI_KEY environment variable raises TON rate limits.
Installation
In SourceWeft
- Open Ton Jetton Risk Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
token-risk MCP (ton-jetton-risk-mcp)
An MCP server that gives an AI agent tools to screen any token for rug-pull / honeypot risk — live, on-chain, free, no API keys.
Covers three ecosystems:
Every tool returns a 0–100 risk score plus concrete flags and the raw facts (taxes, holders, liquidity, owner) as structured JSON.
Data sources: GoPlus token_security, honeypot.is v2 simulation, TonAPI, STON.fi — all live reads, nothing cached, nothing invented.
Install
No global install — run straight from GitHub with npx.
Claude Desktop / Claude Code (claude_desktop_config.json or .mcp.json):
Works the same in any MCP client (Cursor, Windsurf, VS Code, …).
Optional env: TONAPI_KEY — a tonapi.io key raises TON rate limits (works fine without).
Example
"Is
0x4ed4E862860beD51a9570b96d89aF5E1B0Efefedon Base safe to buy?"
The agent calls assess_evm_token_risk and gets back score 0, a passing live
sell simulation, taxes 0/0, open-source contract, deep liquidity — with every
flag it would have raised if any of that were off.
Related
- HTTP pay-per-call version of the same analyzers (x402, USDC):
https://213-165-37-71.sslip.io/v1/evm/token/risk·/v1/jetton/risk— machine-readable schema at/openapi.json - Web checker (browser, free): https://mrvlyouknowwho.github.io/ruglens/
- Telegram: @RugLens_bot
License
MIT
Source: README.md at commit 154cd43
Tools
0Version history
1- v0.2.0LatestSep 16, 2026
Score
40% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.