{"id":"toolsdk-ai-toolsdk-mcp-registry","name":"toolsdk-mcp-registry","af_score":59.0,"security_score":57.2,"reliability_score":30.0,"what_it_does":"An open-source “MCP Registry & Gateway” that lets clients discover and execute Model Context Protocol (MCP) servers through a unified HTTP API. It supports bridging STDIO-based local MCP servers and remote Streamable HTTP servers, includes a sandboxed execution model, and provides an OAuth 2.1 proxy. It also exposes a publicly hosted registry dataset/index via JSON for programmatic discovery (data-only usage).","best_when":"You want a centralized, self-hosted gateway/registry to execute many MCP tools securely (with sandboxing) and to integrate discovery/execution into agent systems via HTTP.","avoid_when":"You cannot operate a Dockerized service (and related dependencies like search) or you need a lightweight local-only MCP client with no registry/gateway overhead.","last_evaluated":"2026-03-30T13:39:51.236815+00:00","has_mcp":false,"has_api":true,"auth_methods":["OAuth 2.1 proxy (for agent integration flows)","Per-request OAuth integration via the gateway (as described in docs references)"],"has_free_tier":false,"known_gotchas":["Tool execution is mediated by the gateway; session-based MCP over Streamable HTTP requires reusing the provided mcp-session-id header (expires after ~30 minutes).","Environment-variable passthrough for MCP tools uses x-mcp-env-* headers; agents must avoid leaking secrets into logs.","Sandbox can be disabled via configuration (MCP_SANDBOX_PROVIDER=LOCAL) which may be unsafe for untrusted tools."],"error_quality":0.0}