{"id":"aarora79-mcp-gateway","name":"mcp-gateway","af_score":49.0,"security_score":47.2,"reliability_score":35.0,"what_it_does":"Provides a deployable MCP Gateway (reverse-proxy via Nginx) and a MCP Registry/UI to register and govern MCP servers, discover tools (including schemas via ListTools), and route MCP client traffic to enabled backend MCP servers using per-service URL paths. Includes health checks and real-time UI updates via WebSockets.","best_when":"You want to standardize and govern MCP server access behind a single endpoint with path-based routing and you can operate the gateway/registry stack.","avoid_when":"You need turnkey SaaS or vendor-managed scaling and SLAs, or you cannot risk that gateway self-signed cert defaults are used without proper TLS configuration.","last_evaluated":"2026-03-30T13:50:12.472043+00:00","has_mcp":true,"has_api":true,"auth_methods":["Basic/battery-included admin login for registry UI and API (ADMIN_USER/ADMIN_PASSWORD)","Optional upstream authorization for backend MCP servers (example notes mention 401 if Polygon API key missing)"],"has_free_tier":false,"known_gotchas":["Because it relies on per-service path routing, agents must use the correct gateway base URL and service path (e.g., /weather/, /currenttime/) to reach the intended MCP server.","TLS defaults mention self-signed certs and HTTP availability; agents may fail verification unless configured to trust the cert or use proper HTTPS setup.","Health checks rely on /sse HEAD probes; a service may be 'enabled' but still fail tool calls if underlying dependencies (e.g., Polygon API key) are misconfigured.","Nginx configuration is dynamically regenerated based on enabled/disabled state; changes may require time for reload/regeneration before agents see updates."],"error_quality":0.0}