Chat with AI and run tools instantly — no API key or third-party login needed.
Let AI agents search the official MCP Registry, inspect server versions, compare remote and package deployment metadata, and monitor registry changes.
Try this workflow
Find registry entries
Search the MCP Registry for browser-related servers and summarize which entries have hosted remotes versus package-only installs.
No API key or third-party login needed. Chat with AI and run tools instantly.
Browse all toolsBuilt for
MCP platform teams, directory operators, developer-tool builders, security reviewers, and agents that need current metadata about published MCP servers
Find registry entries
Turns a broad registry query into deployment-ready discovery context.
Search the MCP Registry for browser-related servers and summarize which entries have hosted remotes versus package-only installs.
Inspect a server
Grounds a server review in the current official registry metadata.
Fetch the latest registry entry for this MCP server name, then summarize its version, lifecycle status, repository, website, packages, and remotes.
Audit a namespace
Checks publication coverage and deployment mix for a registry namespace.
Analyze the `com.mcpbundles/` namespace in the MCP Registry and report active, deprecated, deleted, remote-capable, and package-only counts.
Track recent changes
Supports incremental directory sync and change monitoring.
List registry rows updated since this timestamp and group them by status and deployment type so we can decide what changed downstream.
Does the MCP Registry read API need an API key?
No. The public read endpoints are unauthenticated. Publishing and status edits use namespace-based authentication through the publisher flow.
What can agents inspect in the MCP Registry?
Agents can inspect server names, descriptions, versions, lifecycle status, packages, remote endpoints, repositories, websites, icons, and registry-managed timestamps.
Can agents search by description?
The official search parameter matches server names. Agents can scan pages and apply client-side filters, but the upstream API does not provide semantic description search.
Domain knowledge for MCP Registry — workflow patterns, data models, and gotchas for your AI agent.
The official MCP Registry is the public index of published MCP servers. Its read API is unauthenticated and exposes server metadata, version history, package entries, remote endpoints, repository links, website links, lifecycle status, and update timestamps.
Aggregate mirrored MCP Registry rows by status, namespace, deployment kind, package registry type, and remote transport type. Use namespace for publis...
Compare up to 20 mirrored MCP Registry server entries by full server name. Returns per-server status, version, package/remotes summary, links, and agg...
Fetch one MCP Registry server version from the local mirror by full server name. Use version=latest for the current mirrored row, or pass a specific v...
List all mirrored versions for one MCP Registry server name. The background refresh stores every version row it has seen from list pages.
Search the local mirror of official MCP Registry server rows. Supports cursor pagination, namespace, lifecycle status, deployment type, and MCP App me...
Official Model Context Protocol Registry for discovering published MCP servers, their versions, deployment surfaces, and registry lifecycle status. It provides 5 tools that AI agents can use through the Model Context Protocol (MCP).
Add the MCPBundles server URL to your MCP client configuration (Claude Desktop, Cursor, VS Code, etc.). The URL format is: https://mcp.mcpbundles.com/bundle/mcp-registry. Authentication is handled automatically.
MCP Registry provides 5 tools that can be called by AI agents, along with a SKILL.md that gives your AI agent domain knowledge about when and how to use them.
MCP Registry uses open data APIs — no authentication required.
No. The public read endpoints are unauthenticated. Publishing and status edits use namespace-based authentication through the publisher flow.
Agents can inspect server names, descriptions, versions, lifecycle status, packages, remote endpoints, repositories, websites, icons, and registry-managed timestamps.
The official search parameter matches server names. Agents can scan pages and apply client-side filters, but the upstream API does not provide semantic description search.
Packages describe installable server distributions, often for stdio use. Remotes describe hosted MCP endpoints that clients can connect to over a network transport.
Connect MCP Registry to any MCP client in minutes
The link prefills the Add custom connector dialog — you still review the values and click Add, then Connect to complete OAuth.
MCP Registry and paste the MCP URL into Remote MCP server URL.Custom connectors at claude.ai require a paid Claude plan (Pro, Max, Team, or Enterprise).
More developer tools integrations you might like
Ably is a real-time data streaming platform. Publish and subscribe to messages on channels, track pr...
This server provides AI-powered tools for creating entity-relationship diagrams, helping users visua...
Algolia is a hosted search engine as a service providing developers with tools to index and search t...
Alpic provides advanced AI-driven solutions for various applications, focusing on enhancing user exp...
Amazon Redshift is a fast, fully managed, petabyte-scale data warehouse service in the cloud. Run co...
Workflow: 'Help me ask a great Stack Overflow question'. Search for similar questions to avoid dupli...