{"id":"enkryptai-secure-mcp-gateway","name":"secure-mcp-gateway","af_score":50.2,"security_score":60.2,"reliability_score":22.5,"what_it_does":"secure-mcp-gateway is a Python-based gateway that sits between an MCP client and one or more MCP servers. It authenticates MCP client connections, discovers and caches tools exposed by MCP servers, optionally restricts which tools may be invoked, and can enforce input/output “guardrails” (e.g., injection/toxicity/PII handling) before forwarding requests and after returning responses. It also provides an administrative REST API secured by a generated admin API key (described in README).","best_when":"You want to mitigate common security issues from using MCP tools by adding authentication, tool allowlisting, guardrails, and caching at a single choke point between MCP clients and MCP servers.","avoid_when":"You need guaranteed, documented support for complex failure recovery, idempotency guarantees, or you cannot tolerate potential latency added by guardrail checks and tool discovery/caching.","last_evaluated":"2026-03-30T15:21:50.596555+00:00","has_mcp":true,"has_api":true,"auth_methods":["API key authentication for MCP client connections (\"Unique Key\")","Admin API operations protected by generated admin_apikey (256-character random string)","Optional Enkrypt API key usage for Enkrypt Guardrails integration"],"has_free_tier":false,"known_gotchas":["Tool discovery is dynamic and may involve caching; agents should be prepared for tool list changes when cache expires.","Guardrails can block requests/responses; agents may need to handle policy-block outcomes.","Gateway configuration and allowed-tools allowlisting must be correct; otherwise tool invocation may be restricted or fail."],"error_quality":0.0}