MCP Registry
Central control plane for MCP server registration, tool discovery, allow-lists, health monitoring, and audit — for .
Potencialize seu agente
Instalação do publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
Ainda não há uma versão empacotada no registro. Siga o README do repositório.
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirWithout a registry, MCP servers are ad hoc per-agent connectors with no visibility, governance, or control. The MCP Registry ensures every server, tool, credential binding, and exposure decision is centrally managed and auditable.
> register_mcp_server(name: "github-tools", transport: "stdio", command: "npx -y @modelcontextprotocol/server-github", ...)
{ "server_id": "mcp_github_tools_sta", "version": 1, "status": "registered" }
> test_mcp_server(server_id: "mcp_github_tools_sta")
{ "connectivity": true, "schema_valid": true, "latency_ms": 45, "result": "passed" }
> discover_mcp_tools(server_id: "mcp_github_tools_sta", tools: [...])
{ "snapshot_id": "disc_abc123", "tools_count": 13, "diff": { "added_tools": ["search_repositories", ...] } }
> set_tool_allowlist(server_id: "mcp_github_tools_sta", tool_names: ["search_repositories", "get_file_contents"], ...)
{ "entries": 2, "status": "active" }
> list_mcp_servers()
[{ "id": "mcp_github_tools_sta", "name": "github-tools", "status": "active", "tools_discovered": 13, "tools_allowed": 2 }]
> disable_mcp_server(server_id: "mcp_github_tools_sta")
{ "status": "disabled", "message": "Server removed from active routing. History preserved." }
cargo install mcp-registry
Or build from source:
git clone https://github.com/zavora-ai/mcp-registry
cd mcp-registry
cargo build --release
{
"mcpServers": {
"registry": {
"command": "/path/to/mcp-registry"
}
}
}
Apache-2.0
Part of the ADK-Rust Enterprise MCP server ecosystem.
This server implements the ADK MCP SDK contract:
RUST_LOG env-filter for observabilityThis server is built with rmcp 3.1.2 and requires Rust 1.94.1 or newer. The rmcp 3 rollout retains legacy MCP initialization compatibility and targets MCP protocol revisions 2025-11-25 and 2026-07-28.
This server uses rmcp 3.1.2 and adk-mcp-sdk 0.2 with a minimum supported
Rust version of 1.94.1. It accepts stateless MCP 2026 requests with
per-request protocol, client identity, and capability metadata while retaining
the legacy MCP 2025-11-25 initialize flow for ordinary tools.
discover_mcp_tools, export_mcp_inventoryMcp-Method
and Mcp-Name. The packaged binary currently uses stdio.tools/list returns a public ttlMs of 60,000 for MCP 2026;
rmcp omits the cache fields for legacy clients.Protected tools require MCP_REQUEST_STATE_KEY with at least 32 high-entropy
bytes. All replicas must share that key so sealed approval state can resume on
another instance. Approval state is bound to the client identity, tool, and
arguments and expires after two minutes. Missing identity, invalid state,
rejection, or legacy protocol use fails closed. Task records are process-local
for the current stdio runtime; use a durable task store before deploying the
server behind scale-to-zero HTTP infrastructure.
MCP Registry — central control plane for use with ADK-Rust Enterprise MCP server registration, tool discovery, allow-lists, health, and audit
Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
MCP Registry roda localmente via stdio.
Última verificação: 2026-10-28. MCP Registry — central control plane for use with ADK-Rust Enterprise MCP server registration, tool discovery, allow-lists, health, and audit