mcp-proxy-plus@1.1.0
VERIFIED· not startedPublisher claims: "Production-grade MCP gateway with rate limiting, circuit breaker, RBAC, hot-reload, dashboard, and 14 enterprise features." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
API_ACCESS_TOKENMCP_PROXY_API_KEYor--client-secretConfiguration, not credentials: OTEL_EXPORTER_OTLP_ENDPOINT, SSE_URL- Where it talks to
- no vendor host named in the codeAlso server.local — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names server.local as well as its own vendor. The guard injects API_ACCESS_TOKEN, MCP_PROXY_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-08 and scored it 91/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 1 s · 2 scenarios · 0 deviationsStatic findings
from mcp_proxy.hot_reload import ConfigReloader, create_reload_routeFix: Pin versions and sources; vendor anything fetched at install time.mcp_server_group = parser.add_argument_group("SSE server options")Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.async def test_run_mcp_server_sse_url_logging(Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them."""Test run_mcp_server logs correct SSE URLs."""Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for mcp-proxy-plus@1.1.0 as of 6d ago. This is the package itself, not its dependencies.