io.github.aitools420/onchain-safety-mcp
NPM · @WICKPICS/ONCHAIN-SAFETY-MCP · SCANNED SEP 20
Token-safety for AI agents: rug/honeypot verdict + score across PulseChain, Monad, Base & BSC
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 77 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 758 tokens (~108/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.aitools420/onchain-safety-mcp server?
io.github.aitools420/onchain-safety-mcp runs locally as an npm package, launched with npx -y @wickpics/onchain-safety-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @wickpics/onchain-safety-mcp
claude mcp add aitools420-onchain-safety-mcp -- npx -y @wickpics/onchain-safety-mcp
{
"mcpServers": {
"aitools420-onchain-safety-mcp": {
"command": "npx",
"args": [
"-y",
"@wickpics/onchain-safety-mcp"
]
}
}
} {
"servers": {
"aitools420-onchain-safety-mcp": {
"command": "npx",
"args": [
"-y",
"@wickpics/onchain-safety-mcp"
]
}
}
} codex mcp add aitools420-onchain-safety-mcp -- npx -y @wickpics/onchain-safety-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"aitools420-onchain-safety-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@wickpics/onchain-safety-mcp"
],
"enabled": true
}
}
} openclaw mcp add aitools420-onchain-safety-mcp --command npx --arg -y --arg @wickpics/onchain-safety-mcp
mcp_servers:
aitools420-onchain-safety-mcp:
command: "npx"
args: ["-y", "@wickpics/onchain-safety-mcp"] {
"McpServers": {
"aitools420-onchain-safety-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@wickpics/onchain-safety-mcp"
]
}
}
} assistant mcp add aitools420-onchain-safety-mcp -t stdio -c npx -a -y @wickpics/onchain-safety-mcp
{
"mcpServers": {
"aitools420-onchain-safety-mcp": {
"command": "npx",
"args": [
"-y",
"@wickpics/onchain-safety-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.77 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 14 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@wickpics/onchain-safety-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_ownership Ownership / renounce + privileges ~83
Is ownership renounced, is the contract upgradeable (proxy), and what powers can an active owner still use (mint / blacklist / pause / adjust tax)? Deterministic on-chain read — call before trusting a token long-term.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | the token contract address (0x…) |
| chain | string | yes | chain the token is on |
No output schema declared.
No examples provided.
check_token_safety Check token safety ~159
Scam/safe verdict for an ERC-20 token on PulseChain, Monad, Base, or BSC. Returns verdict (SAFE / LOW_RISK / CAUTION / HIGH_RISK / LIKELY_RUG / NOT_A_TOKEN / UNKNOWN), a 0-100 score, confidence, and the evidence checks (contract risk, liquidity depth, honeypot transfer-sim, LP-burn). Call this before interacting with, buying, or accepting an unknown token. Informational only — an automated assessment that can be wrong; a SAFE score is not a guarantee, and this is not financial advice.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | the token contract address (0x…) |
| chain | string | yes | chain the token is on |
No output schema declared.
No examples provided.
exit_safety Exit safety / liquidity depth ~138
Can you sell $X of a token at acceptable slippage? Size-aware price-impact check (on-chain reserves + routed quote) plus the safety verdict. Call this BEFORE buying a position you may need to exit, or before accepting a token as payment. Informational only — an automated assessment that can be wrong; not financial advice.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | chain the token is on |
| maxSlippage | number | – | max acceptable slippage percent (default 10) |
| sizeUsd | number | yes | position size in USD you would need to exit |
| token | string | yes | the token contract address (0x…) |
No output schema declared.
No examples provided.
fresh_rug_radar Fresh-pool rug radar ~84
The most recently created liquidity pools, each safety-scored the moment it appeared (verdict, 0-100 score, seconds-since-creation). New tokens are where the rugs are — call this to see what just launched and whether it is safe. Free tier returns the last 20 scored pools; a paid key unlocks the fuller real-time feed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
safe_to_interact Safe to interact? (composite) ~94
One call before touching a contract: bundles the safety verdict + ownership/privileges into a single recommendation — SAFE_TO_INTERACT / CAUTION / DO_NOT_INTERACT — with reasons. The de-risked "should I touch this?" answer for an agent mid-execution.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | the contract/token address (0x…) |
| chain | string | yes | chain the token/contract is on |
No output schema declared.
No examples provided.
wallet_approvals Wallet approval scanner ~86
Enumerate a wallet's active ERC-20 approvals (allowances granted to spender contracts) and flag the unlimited ones — the classic wallet-drainer vector. Call to audit what could quietly drain a wallet. Scans a recent block window.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | chain the wallet is on |
| owner | string | yes | the wallet address to scan (0x…) |
No output schema declared.
No examples provided.
wallet_poison_check Address-poisoning scanner ~114
Scan a wallet's recent incoming transfers for address-poisoning attacks — dust/zero-value transfers from lookalike addresses (first-4+last-4 chars matching a real counterparty the wallet has paid) seeded to trick a copy-paste of the wrong address. Call before sending to a "recently used" address to avoid pasting a poisoned lookalike.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | chain the wallet is on |
| owner | string | yes | the wallet address to scan (0x…) |
No output schema declared.
No examples provided.
What is the io.github.aitools420/onchain-safety-mcp server?
io.github.aitools420/onchain-safety-mcp is listed in the public MCP registry as io.github.aitools420/onchain-safety-mcp. Token-safety for AI agents: rug/honeypot verdict + score across PulseChain, Monad, Base & BSC. This page covers its npm package (@wickpics/onchain-safety-mcp).
Is the io.github.aitools420/onchain-safety-mcp server safe to use?
io.github.aitools420/onchain-safety-mcp scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.aitools420/onchain-safety-mcp server expose?
io.github.aitools420/onchain-safety-mcp exposes 7 tools: check_token_safety, fresh_rug_radar, exit_safety, check_ownership, safe_to_interact, and 2 more. Their descriptions and schemas cost roughly 758 tokens of context every time the server is loaded.
Is the io.github.aitools420/onchain-safety-mcp server still maintained?
io.github.aitools420/onchain-safety-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.aitools420/onchain-safety-mcp server under?
io.github.aitools420/onchain-safety-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.