io.github.aitools420/onchain-safety-mcp
Token-safety for AI agents: rug/honeypot verdict + score across PulseChain, Monad, Base & BSC
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 »).
@wickpics/onchain-safety-mcpclaude mcp add onchain-safety-mcp -e 'ONCHAIN_API_KEY=<your onchain_api_key>' -- npx -y @wickpics/onchain-safety-mcp@0.2.0
{
"mcpServers": {
"onchain-safety-mcp": {
"command": "npx",
"args": [
"-y",
"@wickpics/onchain-safety-mcp@0.2.0"
],
"env": {
"ONCHAIN_API_KEY": "<your onchain_api_key>"
}
}
}
}
Variables d'environnement
ONCHAIN_API_KEYsecret Optional wsk_ key for the paid deep tier (omit for the free rate-limited tier).
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
onchain-safety-mcp
MCP (Model Context Protocol) server that gives any AI agent on-chain token-safety tools for PulseChain, Monad, Base, and BSC — including PulseChain, which the major token-safety APIs (GoPlus, Honeypot.is) don't support at all (verified June 2026). If your agent touches PulseChain, this is the safety check.
It is a thin stdio client over the hosted API at onchain.wick.pics
(engine wick-safe/0.3). Every check is deterministic on-chain analysis — no LLM in the
verdict path, so results are fast, cheap, and reproducible: contract-risk heuristics,
liquidity depth, honeypot transfer-simulation, LP-burn, ownership/renounce + privilege
detection, upgradeable-proxy detection, and a wallet approval (drainer) scanner. The free tier
needs no key. Informational, not financial advice.
Tools
| tool | what it answers |
|---|---|
check_token_safety({ chain, address }) | Is this token a scam? Verdict (SAFE … LIKELY_RUG), 0–100 score, evidence checks. |
fresh_rug_radar() | What just launched, and is it safe? Last 20 freshly-created pools, safety-scored at creation. |
exit_safety({ chain, token, sizeUsd, maxSlippage? }) | Could I sell $X of this at acceptable slippage? Size-aware price impact + safety verdict. |
check_ownership({ chain, address }) | Is ownership renounced / upgradeable, and what can an active owner still do (mint, blacklist, pause, tax)? |
safe_to_interact({ chain, address }) | One call → SAFE_TO_INTERACT / CAUTION / DO_NOT_INTERACT, bundling safety + ownership, with reasons. |
wallet_approvals({ chain, owner }) | A wallet's active ERC-20 approvals, flagging unlimited grants — the drainer vector. |
wallet_poison_check({ chain, owner }) | Address-poisoning scan: dust/look-alike transfers in a wallet's history that mimic a real counterparty to trick a paste-and-send of the wrong address. |
chain: pulsechain | monad | base | bsc · token/address: 0x… contract address.
Agents should call check_token_safety / exit_safety before interacting with, buying, or
accepting an unknown token.
Install (any MCP client — Claude Desktop, agent frameworks)
{
"mcpServers": {
"onchain-safety": {
"command": "npx",
"args": ["-y", "github:aitools420/onchain-safety-mcp"],
"env": { "ONCHAIN_API_KEY": "wsk_…" }
}
}
}
ONCHAIN_API_KEY is optional — omit it for the free rate-limited tier. A wsk_ key
unlocks the paid deep tier (get one at onchain.wick.pics).
Pay-per-call for autonomous agents (x402)
The same engine is available with no signup and no key via the x402 pay-per-call protocol — agents pay USDC on Base per request. Machine-readable index of every paid route (token-safety, fresh-rug radar, exit-safety):
https://onchain.wick.pics/.well-known/x402.json
Human docs: onchain.wick.pics/agents
Env
| var | default | purpose |
|---|---|---|
ONCHAIN_API_BASE | https://onchain.wick.pics | API host |
ONCHAIN_API_KEY | (none — free tier) | wsk_ key for the paid deep tier |
License
MIT
Questions fréquentes
Qu'est-ce que io.github.aitools420/onchain-safety-mcp ?
Token-safety for AI agents: rug/honeypot verdict + score across PulseChain, Monad, Base & BSC
Comment installer io.github.aitools420/onchain-safety-mcp ?
Il s'exécute sur votre machine. Dans Claude Code : claude mcp add onchain-safety-mcp -e 'ONCHAIN_API_KEY=<your onchain_api_key>' -- npx -y @wickpics/onchain-safety-mcp@0.2.0. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour io.github.aitools420/onchain-safety-mcp ?
Oui. Il attend ONCHAIN_API_KEY, à renseigner dans sa configuration.
io.github.aitools420/onchain-safety-mcp est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient io.github.aitools420/onchain-safety-mcp ?
Il est publié par aitools420. 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.