LIVE OFFICIAL METADATA · USER-INITIATED · NO FAKE RANKINGS
Official MCP Registry Browser & Trust Checklist
Search the live official Model Context Protocol Registry, inspect the declared package or remote transport, and review what the record does—and does not—prove before connecting a server to Claude, Codex, Cursor, VS Code, Gemini CLI or another MCP client.
Important boundary: Registry publication verifies namespace and package metadata according to the Registry process. It is not a security audit, maintenance score, uptime guarantee or permission review.
Search latest Registry records
The official API searches server names. Leave the field empty to load the next page of latest-version records.
Official API v0.1 · preview
Network disclosure: only after you submit, the search term goes directly from your browser to registry.modelcontextprotocol.io. It is not sent through or stored by EasyTool. Never paste a token or private endpoint.
No external request has been made. Search when you are ready.
What an official Registry record proves
It can prove
The publisher satisfied the Registry's namespace and package-validation process at publication.
The record declares a name, version and optional repository, package, remote transport and input metadata.
The official status metadata indicates whether that version is active, deleted or otherwise changed.
It cannot prove
That source code, tools or dependencies are safe.
That the repository is maintained, the endpoint is available or the description remains accurate.
That the server follows least privilege, handles OAuth correctly or cannot expose data through tool calls.
A five-minute MCP server admission review
Confirm identity: compare the Registry namespace, repository owner, package publisher and vendor documentation. Similar names are not equivalent.
Inspect the artifact: open the exact package version or remote endpoint documentation. Review install scripts, dependencies, release history and unresolved security reports.
Map permissions: list files, commands, network hosts, repositories, databases and account actions each tool can reach. Start read-only and narrow.
Scope credentials: create a dedicated token with the minimum permissions and expiry. Do not copy secrets into project JSON or prompts.
Verify behavior: connect it in a disposable workspace, inspect tools/list, run one bounded action and record how to revoke access.
From discovery to a safe client configuration
This browser intentionally does not invent an install command from incomplete metadata. Copy the Registry ID or metadata, confirm the publisher's installation documentation, then use the MCP Config Doctor to validate or convert the client configuration. Estimate exposed schema context with the MCP Token Budget Analyzer, and diagnose remote authorization separately with the MCP OAuth Debugger.
Page reviewed: 2026-08-02. Live records come from the official API only after a user-initiated request. The Registry remains a preview service, so API behavior and records can change.