Home / MCP registry index / io.github.ak10082247-max/rugshield-402

RugShield 402

io.github.ak10082247-max/rugshield-402 in the official MCP registry. Endpoint https://rugshield-402.onrender.com/mcp. Source: github.com/ak10082247-max/rugshield-402.

The registry describes it as: Real-time token contract safety scanner and honeypot auditor via x402 on Base.

Tools it advertises

analyze_liquidity check_honeypot rugshield_pre_swap_scan rugshield_audit_liquidity_lock_verify rugshield_audit_holder_cluster_map rugshield_audit_swap_simulation_proof rugshield_audit_cross_chain_bridge_risk rugshield_risk_institutional_token_report rugshield_token_screener rugshield_smart_money_netflow rugshield_smart_money_dex_trades rugshield_tgm_who_bought_sold rugshield_tgm_holders rugshield_profiler_address_current_balance

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-ak10082247-max-rugshield-402/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-ak10082247-max-rugshield-402)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers