Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.aitools420/onchain-safety-mcp

NPM · @WICKPICS/ONCHAIN-SAFETY-MCP · SCANNED AUG 3

Token-safety for AI agents: rug/honeypot verdict + score across PulseChain, Monad, Base & BSC

−15 this week 65 Trust /100
Trust breakdown (6 categories)

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 →

Supply Chain Security86
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability77
  • 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @wickpics/onchain-safety-mcp

# add to Claude Code
claude mcp add aitools420-onchain-safety-mcp -- npx -y @wickpics/onchain-safety-mcp
# add to Codex CLI
codex mcp add aitools420-onchain-safety-mcp -- npx -y @wickpics/onchain-safety-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "aitools420-onchain-safety-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@wickpics/onchain-safety-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add aitools420-onchain-safety-mcp --command npx --arg -y --arg @wickpics/onchain-safety-mcp
# ~/.hermes/config.yaml
mcp_servers:
  aitools420-onchain-safety-mcp:
    command: "npx"
    args: ["-y", "@wickpics/onchain-safety-mcp"]
// mcp.json
{
  "mcpServers": {
    "aitools420-onchain-safety-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@wickpics/onchain-safety-mcp"
      ]
    }
  }
}
Changelog

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.

  • 3 Aug 26 +14
    • Provenance: unverified → fail security
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • Maintenance: unverified → pass functional
    • Dependency health: unverified → partial functional
    • License: unverified → pass functional
    • Licence: MIT functional
  • 2 Aug 26 +15
    • Malware scan: unverified → pass security
  • 1 Aug 26 +31
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 functional
    • MCP protocol: unverified → pass functional
  • 31 Jul 26 −57
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −18
    • Malware scan: pass → unverified security
  • 27 Jul 26 +37
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 43

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Analysed npm/@wickpics/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 94 packages

94 packages in the resolved dependency tree · 94 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 7 exposed · ~758 tokens

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.

Tool Tokens
check_ownership ~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.

NameTypeReqDescription
addressstringyesthe token contract address (0x…)
chainstringyeschain the token is on

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
addressstringyesthe token contract address (0x…)
chainstringyeschain the token is on

No output schema declared.

No examples provided.

exit_safety ~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.

NameTypeReqDescription
chainstringyeschain the token is on
maxSlippagenumbermax acceptable slippage percent (default 10)
sizeUsdnumberyesposition size in USD you would need to exit
tokenstringyesthe token contract address (0x…)

No output schema declared.

No examples provided.

fresh_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 ~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.

NameTypeReqDescription
addressstringyesthe contract/token address (0x…)
chainstringyeschain the token/contract is on

No output schema declared.

No examples provided.

wallet_approvals ~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.

NameTypeReqDescription
chainstringyeschain the wallet is on
ownerstringyesthe wallet address to scan (0x…)

No output schema declared.

No examples provided.

wallet_poison_check ~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.

NameTypeReqDescription
chainstringyeschain the wallet is on
ownerstringyesthe wallet address to scan (0x…)

No output schema declared.

No examples provided.