Production MCP gateway: JWT auth, rate limiting, spending controls, audit log. mcp-guard serve --config mcp-guard.yaml
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"bonanza-mcp-guard","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# mcp-guard [](https://github.com/c6zks4gssn-droid/mcp-guard/actions/workflows/ci.yml) [](https://pypi.org/project/bonanza-mcp-guard/) [](LICENSE) [](https://pypi.org/project/bonanza-mcp-guard/) **Put auth, rate limits, spend caps, and audit logs in front of any MCP server — without changing the server.** ```bash pip install "bonanza-mcp-guard[yaml]" mcp-guard scan mcp-guard serve --config mcp-guard.yaml ``` > **PyPI:** package [`bonanza-mcp-guard`](https://pypi.org/project/bonanza-mcp-guard/) (name `mcp-guard` was taken). CLI is still `mcp-guard`.  Sits in front of any MCP server over stdio. Zero required dependencies. Complements static scanners like [mcp-scan](https://github.com/invariantlabs-ai/mcp-scan) with a **runtime stdio gateway** (auth, limits, audit). ## Why mcp-guard? | Without mcp-guard | With mcp-guard | |---|---| | Any agent calls any tool | Agent must authenticate (API key / JWT) | | No spend ceiling | Per-session spend caps, per-hour rate limits | | No audit trail | Every request logged to JSONL | | Server exposed directly | Gateway wraps server — zero code changes | Complements static scanners like [mcp-scan](https://github.com/invariantlabs-ai/mcp-scan) with a **runtime stdio gateway** (auth, limits, audit). --- ## The problem Security research in 2026 reported **1,800+ internet-exposed MCP endpoints** with **no authentication**. Any MCP client can invoke tools with no identity, no spend ceiling, and no audit trail. `mcp-guard` adds a gateway layer — Claude Desktop, Cursor, Windsurf, or custom agents talk to `mcp-guard`; it talks to your real MCP server. --- ## 30-second try ```bash pip install "bonanza-mcp-guard[yaml]" mcp-guard scan…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.