Home / MCP registry index / io.github.stand-out-of-my-sun/diogenes-web3-security-mcp
Diogenes Web3, DeFi & 402 Security MCP
io.github.stand-out-of-my-sun/diogenes-web3-security-mcp in the official MCP registry.
Endpoint https://diogenes-micro-gateway.corinth.workers.dev/mcp/web3-security. Source: github.com/stand-out-of-my-sun/diogenes-web3-security-mcp.
The registry describes it as: Smart contract audit oracles, Solana risk analysis, MEV defense & HTTP 402 verifiers.
We read its 15 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
audit_smart_contract_code scan_solana_cpi_reentrancy evaluate_solana_token_risk inspect_solana_token_liquidity track_solana_whale_flows estimate_solana_priority_fees decode_eip712_permit_signature simulate_evm_transaction_calldata evaluate_dex_mev_risk detect_address_poisoning_scam verify_http402_payment_challenge estimate_bitcoin_mempool_fees plan_bitcoin_utxo_consolidation calculate_spot_swap_rate compare_crosschain_bridge_routes
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-stand-out-of-my-sun-diogenes-web3-security-mcp)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.