rug-check
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@rug-checkcheck token 0x4ed4e862860bed51a9570b96d89af5e1b0efefed on base"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
rug-check π¨
On-chain rug-pull & honeypot risk screen for ERC-20 tokens β for AI agents and traders.
Give it a token address and get a SAFE / CAUTION / HIGH-RISK verdict (0β100 score) in one call, built entirely from live public-RPC reads β no API key, no node, no signup.
rug-check is an automated on-chain risk screen, not financial advice or a safety guarantee. It pattern-matches deployed bytecode and reads chain state; it cannot catch every scam (off-chain admin keys, novel honeypots) and may flag benign contracts. Always do your own research.
Why it exists (the moat)
An AI coding/trading agent that "just reads the chain" does not know:
Which dangerous functions the token's deployed bytecode exposes β
mint,blacklist,pause,setFees,setMaxTxβ the levers used to trap or dilute holders.Whether ownership is renounced, or an active owner can still call those powers after you buy.
How concentrated supply is in the owner/deployer wallet (dump risk).
Whether a DEX liquidity pair exists, how deep it is, and whether the LP tokens are locked or burned β the single thing that decides if the deployer can pull all liquidity (the literal "rug pull").
rug-check ABI-encodes and batches all of that, decodes the bytecode, scores it, and returns one verdict.
Related MCP server: safeagent-token-safety
What it checks
Check | What it tells you |
Owner powers | scans runtime bytecode for |
Ownership | renounced vs active owner ( |
Concentration | % of total supply held by the owner wallet |
Liquidity | UniswapV2/Pancake pair reserves vs wrapped-native, depth, thin-liquidity flag |
LP lock/burn | % of LP supply in burn address or known lockers (Pinksale, Unicrypt, Team.Financeβ¦) |
Proxy | EIP-1967 upgradeable-proxy detection (behaviour can change post-launch) |
Chains: Ethereum, Base, BSC, Polygon, Arbitrum.
Use as an MCP server (free)
{
"mcpServers": {
"rug-check": { "command": "npx", "args": ["-y", "rugshield-mcp"] }
}
}Tools:
rug_check_tokenβ{ chain, address }β full risk report.rug_check_manyβ up to 10{ chain, address }β batch verdicts.
Or connect over HTTP at POST /mcp.
Free HTTP API
GET /check?chain=base&address=0x4ed4e862860bed51a9570b96d89af5e1b0efefed
GET /check?chain=ethereum&address=0x6b175474e89094c44da98b954eedeac495271d0fRate-limited 30/h/IP.
Pay-per-call (x402)
The /pro/* routes are gated by x402. Your agent pays $0.25 USDC per call automatically β no sign-up, no API key. Settles on-chain (Base) to the operator wallet.
GET /pro/check?chain=base&address=0x...
GET /pro/check_many?tokens=base:0x..,bsc:0x..Discovery: GET /openapi.json (with x-payment-info) and GET /.well-known/x402.
Develop
npm install
npm run build
npm run test:engine # offline unit tests + live on-chain sanity checks
npm run dev:http # local HTTP server on :8080 (payments OFF unless configured)
npm run dev:mcp # stdio MCP serverMIT Β© rug-check
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Baneado98/rug-check'
If you have feedback or need assistance with the MCP directory API, please join our Discord server