mcpField
O
onchain-safety-mcp

onchain-safety-mcp

Local
github.com/aitools420Security0Updated 17w ago

About onchain-safety-mcp

onchain-safety-mcp provides on-chain safety checks for AI agents handling tokens on PulseChain, Monad, Base, and BSC. Its verdicts use deterministic on-chain analysis rather than an LLM.

Key features

  1. 01Checks token safety scores and evidence
  2. 02Scans newly created liquidity pools
  3. 03Estimates sell slippage for a given size
  4. 04Checks ownership and contract privileges
  5. 05Scans wallet approvals and address poisoning

Use cases

  1. 01Check an unknown token before interacting
  2. 02Assess sell size and price impact
  3. 03Find risky approvals in a wallet
  4. 04Review actions available to a token owner

MCP support

This MCP server gives AI agents on-chain token-safety tools through a hosted API, supporting PulseChain, Monad, Base, and BSC. The free tier can be used without an API key.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"aitools420-onchain-safety": {
"command": "npx",
"args": [
"-y",
"@wickpics/onchain-safety-mcp"
],
"env": {
"ONCHAIN_API_KEY": "<ONCHAIN_API_KEY>"
}
}
}
}
Run commandnpx -y @wickpics/onchain-safety-mcp
Environment variables to set
ONCHAIN_API_KEYSecretOptional wsk_ key for the paid deep tier (omit for the free rate-limited tier).

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@wickpics/onchain-safety-mcp0.2.0

Tools

7

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
chainenumYeschain the token is onpulsechain | monad | base | bsc
addressstringYesthe token contract address (0x…)

Details

From the project README

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

toolwhat 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

vardefaultpurpose
ONCHAIN_API_BASEhttps://onchain.wick.picsAPI host
ONCHAIN_API_KEY(none — free tier)wsk_ key for the paid deep tier

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.