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

StealthGuard 402

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

The registry describes it as: Stealth web extraction, Polymarket alpha, and on-chain pre-trade gating via x402 on Base.

Tools it advertises

stealth_scrape_and_sanitize polymarket_alpha_divergence pre_trade_agent_gate polymarket_top_whales polymarket_crypto_odds base_trending_tokens defi_yield_radar hackernews_ai_digest security_prompt_firewall security_x402_endpoint_verifier research_deep_web_dossier oracle_perp_funding_and_basis alpha_polymarket_whale_orderflow security_attestation_bundle research_topic_news_scanner

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-stealthguard-402/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-ak10082247-max-stealthguard-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