mcpbeat Sign in

Onchain Risk MCP Server

answering

Onchain Risk MCP is answering right now. Last checked 13 min ago. It exposes 2 tools.

Audits any Base/EVM address for bytecode risk, proxy patterns, honeypot selectors, and balance.

Uptime history 68 hours of history · worst hour 75%
68 hours agonow
100.0%
Uptime 24h
92 of 92 checks
2
Tools
read from the server
205 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 13

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 14 October 2026. No other catalogue keeps this.

16 Oct 2 tools changed the parameters they ask for4 times that day get_agent_wallet_status, scan_onchain_address_risk
16 Oct 2 tool descriptions were rewritten get_agent_wallet_status, scan_onchain_address_risk
16 Oct a tool changed version
15 Oct 2 tool descriptions were rewritten get_agent_wallet_status, scan_onchain_address_risk
15 Oct 2 tools changed the parameters they ask for get_agent_wallet_status, scan_onchain_address_risk
14 Oct a tool description was rewritten scan_onchain_address_risk
14 Oct a tool changed the parameters it asks for scan_onchain_address_risk
and 2 more, back to 14 October 2026

Onchain Risk MCP missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add onchain-risk-mcp --transport http https://onchain-risk-72343955726.us-central1.run.app/mcp/onchain-risk
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "onchain-risk-mcp": {
      "url": "https://onchain-risk-72343955726.us-central1.run.app/mcp/onchain-risk"
    }
  }
}
~/.codex/config.toml
[mcp_servers.onchain-risk-mcp]
url = "https://onchain-risk-72343955726.us-central1.run.app/mcp/onchain-risk"
.cursor/mcp.json
{
  "mcpServers": {
    "onchain-risk-mcp": {
      "url": "https://onchain-risk-72343955726.us-central1.run.app/mcp/onchain-risk"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "onchain-risk-mcp": {
      "url": "https://onchain-risk-72343955726.us-central1.run.app/mcp/onchain-risk"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

agent
get_agent_wallet_status
Show an agent's account: free calls used (of 5), prepaid USD balance, total spent, total calls and tokens saved. Free: it never charges or uses a free call. Call it before a batch of paid calls, or after a top-up to confirm the credit arrived. It does not process content or take payments; use the other tools on this server for that. Returns JSON with free_calls_used, balance_usd, total_spent_usd, total_tokens_saved.
scan
scan_onchain_address_risk
Audits any Base EVM 0x contract or Solana SPL Mint for proxy patterns, GoPlus honeypot flags, and freeze authority. Use it when your task needs this for one address; this endpoint offers only this tool and get_agent_wallet_status. Read-only; results are cached for 1 hour. $0.02 per call. Returns JSON with the result under data. Pricing: the first 5 calls per agent_id are free and failed calls are never charged. After that the tool returns a payment-required message (not an error) with a Stripe top-up link (from $2) and Base/Solana USDC addresses; pay, then repeat the same call with the same agent_id, or add tx_hash after a USDC transfer.

Endpoints

URLTransportStateLatencyChecked
https://onchain-risk-72343955726.us-central1.run.app/mcp/onchain-risk streamable-http answering 225 ms 13 min ago

Alternatives to Onchain Risk MCP

same job, measured the same way
VPNDetection
by vpndetection-io

VPN, proxy, Tor, hosting and CDN detection for any IP address, from the VPNDetection API.

666 installs/wk answering
Automaton Token Safety
by baianomarceloeduardo-jpg

Base L2 token safety for AI agents: honeypot scans, swap simulation, approval and liquidity risk.

51 installs/wk 20 tools answering
RugRadar
by jimmybr-pdx

Rug-pull, token-safety and honeypot risk checks for Solana and EVM tokens. $0.01 per call.

3 tools answering
T
Trust Check
by gmahar82-stack

Base crypto safety for agents: honeypot/tax test, address poisoning, rug feed, creator record.

4 tools answering
Free Base Blockchain Tools
by agentsapi

13 free Base tools: address labels, tx explain, balances, receipts, gas, logs, bytecode.

14 tools answering
Vetagent
by vetagent

Pre-trade safety check for AI agents: honeypot, tax, liquidity and rug risk before you buy.

3 tools answering
ContractLens
by appin60-contractlens-api

EVM token risk checks, x402 payability check for sellers, address classifier and live gas.

5 tools answering
MAD Synapse · Wallets & Risk
by maddegen-agent

Pre-trade safety + wallets: Solana/EVM token risk, honeypots, counterparties, balances, txs, CVEs.

15 tools answering

Onchain Risk MCP — questions

Answers built from our own checks of this server.

What can Onchain Risk MCP do?
It exposes 2 tools, read directly from the server on our last check. Among them: get_agent_wallet_status, scan_onchain_address_risk. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Onchain Risk MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 205 ms. The bar chart above shows every period we have measured.
How do I connect Onchain Risk MCP?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Onchain Risk MCP need an API key?
No. Onchain Risk MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Onchain Risk MCP?
It answers our handshake in 205 ms on average, which is faster than 61% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.