# io.github.aitools420/onchain-safety-mcp (npm · @wickpics/onchain-safety-mcp)

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

- Trust score: 65/100 (medium)
- Change this week: −15
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `@wickpics/onchain-safety-mcp`: 65/100 (this document), [markdown](https://verifymcp.io/servers/aitools420-onchain-safety-mcp/wickpics-onchain-safety-mcp.md), [page](https://verifymcp.io/servers/aitools420-onchain-safety-mcp/wickpics-onchain-safety-mcp)

## Channel facts

- Registry: `npm`
- Package: `@wickpics/onchain-safety-mcp`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 86/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 29 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 758 tokens (~108/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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

### Claude

```bash
claude mcp add aitools420-onchain-safety-mcp -- npx -y @wickpics/onchain-safety-mcp
```

### Codex

```bash
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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add aitools420-onchain-safety-mcp --command npx --arg -y --arg @wickpics/onchain-safety-mcp
```

### Hermes

```yaml
mcp_servers:
  aitools420-onchain-safety-mcp:
    command: "npx"
    args: ["-y", "@wickpics/onchain-safety-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "aitools420-onchain-safety-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@wickpics/onchain-safety-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 65, +14)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] License: unverified → pass
- [functional] Licence: MIT

### 2026-08-02 (score 51, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-08-01 (score 36, +31)

- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass

### 2026-07-31 (score 5, −57)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 62, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-27 (score 80, +37)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 43)

First indexed and scored.

## MCP tools (7)

### `check_token_safety` (~159 tokens)

Check token safety

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.

Input parameters:

- `address` (string, required): the token contract address (0x…)
- `chain` (string, required): chain the token is on

### `fresh_rug_radar` (~84 tokens)

Fresh-pool rug radar

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.

### `exit_safety` (~138 tokens)

Exit safety / liquidity depth

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.

Input parameters:

- `chain` (string, required): chain the token is on
- `maxSlippage` (number): max acceptable slippage percent (default 10)
- `sizeUsd` (number, required): position size in USD you would need to exit
- `token` (string, required): the token contract address (0x…)

### `check_ownership` (~83 tokens)

Ownership / renounce + privileges

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.

Input parameters:

- `address` (string, required): the token contract address (0x…)
- `chain` (string, required): chain the token is on

### `safe_to_interact` (~94 tokens)

Safe to interact? (composite)

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.

Input parameters:

- `address` (string, required): the contract/token address (0x…)
- `chain` (string, required): chain the token/contract is on

### `wallet_approvals` (~86 tokens)

Wallet approval scanner

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.

Input parameters:

- `chain` (string, required): chain the wallet is on
- `owner` (string, required): the wallet address to scan (0x…)

### `wallet_poison_check` (~114 tokens)

Address-poisoning scanner

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.

Input parameters:

- `chain` (string, required): chain the wallet is on
- `owner` (string, required): the wallet address to scan (0x…)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/aitools420-onchain-safety-mcp/wickpics-onchain-safety-mcp#diagnostics

## Score history

- 2026-08-03: 65
- 2026-08-02: 51
- 2026-08-01: 36
- 2026-07-31: 5
- 2026-07-30: 62
- 2026-07-29: 80
- 2026-07-27: 80
- 2026-07-26: 43

## Links

- npm package: https://www.npmjs.com/package/@wickpics/onchain-safety-mcp
- Socket report: https://socket.dev/npm/package/@wickpics/onchain-safety-mcp
- Repository: https://github.com/aitools420/onchain-safety-mcp
- Changelog RSS feed: https://verifymcp.io/servers/aitools420-onchain-safety-mcp/wickpics-onchain-safety-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/aitools420-onchain-safety-mcp/wickpics-onchain-safety-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/aitools420-onchain-safety-mcp/wickpics-onchain-safety-mcp