io.github.GuardBee/security-proxy

MCP gateway: many servers, one policy, lethal-trifecta blocking, PII masking, audit log

needs env probed 2026-10-19

MCP error -32000: Connection closed
[guardbee-proxy] Fatal error: No proxy target configured. Use: guardbee-proxy -- <command> [args]
Or create a guardbee-proxy

Run it: npx -y @guardbee/mcp-security-proxy@1.20.0 (stdio, probed in a container with the network off)
Host: npmjs.com
Repository: https://github.com/GuardBee/guardbee-mcp
Registry: active, updated 2026-10-19 · registry entry
Reachable: 0 of the last 1 probe

Badge for the README

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Atom feed

A mail when this server changes

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

For the publisher

The server exits because an environment variable is missing. The probe starts the package without secrets. A server that starts without secrets and asks for them on the first tool call is measured.