Rugcheck MCP Server

Rugcheck MCP server exists for a simple reason — assistants are far more useful when they can act on Rugcheck directly instead of describing what you should do. On-chain Solana token safety — screen for rugs/honeypots and execute MEV-protected swaps.

What you get

A lightweight MCP server that reads a Solana token's mint directly from the chain to screen for the common rug & honeypot traps before your agent trades — active mint/freeze authority and dangerous Token-2022 extensions (permanent delegate, transfer hooks, non-transferable, pausable) — then, for tokens that pass, builds the buy as an unsigned Jupiter transaction carrying a small Jito tip for faster inclusion. You sign it; the server never holds keys.

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

What the assistant can call

Once Rugcheck is connected, these are the calls the assistant has available:

• scan_token — full safety report in one call: authority, Token-2022 traps, honeypot, liquidity & holder concentration → SAFE/CAUTION/DANGER + a 0–100 score
• is_safe — quick yes/no gate: one boolean before you trade
• verify_token_safety — on-chain audit: mint/freeze authority + Token-2022 traps + live market
• check_authorities — mint / freeze authority and extension detection
• simulate_sell — can the token actually be sold? (honeypot check)
• simulate_trade — full round-trip (buy then sell back): real entry/exit cost & round-trip loss %
• check_liquidity — DEX liquidity, 24h volume, age, buys/sells
• holders_breakdown — top-holder concentration (dump risk)
• token_age — freshness + real trading activity
• rug_forecast — heuristic rug ETA: probability + urgency window + factors
• scammer_dna — intent score (0–100): how much the token's structure looks like a deliberate scam
• check_deployer — the wallets that hold power over the token

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Rugcheck.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the rugcheck mcp server does with a few real requests.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Rugcheck's toolset — scan_token, is_safe, verify_token_safety and 11 more — is a fair guide to whether it matches your workflow. It is maintained by MrWizardlyLoaf; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.