FastMCP
FastMCP is the most widely used MCP server framework in any language, with 98M+ downloads last month. Horizon Registry is the enterprise MCP registry from the team that helped define how modern MCP servers get built.
A GitHub MCP server here. A Jira server there. Someone builds a Slack integration. Then a Salesforce connector. Then ten more.
Then someone forks one. Then nobody remembers which version has the security patch. Then an agent uses the wrong one to access customer data.
Public directories help you discover what exists. But your organization still needs to know which servers are approved, who owns them, and which version is safe for production.
That's what a private MCP registry solves.
Public vs. Private
| Capability | Public Directories | Horizon Registry |
|---|---|---|
| What it catalogs | Public DirectoriesOpen-source MCP servers anyone can publish | Horizon RegistryYour organization's approved MCP servers, internal and external |
| Who decides what's listed | Public DirectoriesAnyone | Horizon RegistryYour platform team |
| Approval workflow | Public DirectoriesNone | Horizon RegistryBuilt-in version approval and deprecation |
| Ownership | Public DirectoriesCommunity maintained | Horizon RegistryDesignated owners for every server |
| Access control | Public DirectoriesPublic | Horizon RegistryPrivate and role-based |
| Custom or internal servers | Public DirectoriesLimited or unsupported | Horizon RegistryFirst-class support |
| Remix servers | Public DirectoriesNot supported | Horizon RegistryCompose purpose-built endpoints for each team |
Once you've decided what's approved, Gateway controls access and Deploy ships new servers.
MCP Server Catalog
Search MCP servers by name, capability, or connected system, from GitHub and Jira to Slack, Salesforce, databases, and more.
Every MCP server has a designated owner. Know who built it, who maintains it, and who to contact when a team needs access or a capability needs to change.
Browse the tools, resources, and prompts each MCP server exposes. Understand what an agent will actually touch before you approve it for production.
Pin approved versions for production use, flag deprecated servers, and keep every team on the version security and platform teams actually want in use.
Common Integrations
Remix Servers
Your engineering team needs GitHub, Jira, and PagerDuty, but not Salesforce. Your sales team needs Salesforce and HubSpot, but not production databases.
Remix servers let you combine tools from any MCP server, first-party or third-party, into a single purpose-built endpoint. One Engineering Assistant server with the right tools for incident response. One Sales Ops server with the exact systems needed for account work.
Engineering Assistant
GitHub + Jira + PagerDuty for triage, release checks, and incident workflows.
Sales Ops
Salesforce + HubSpot for pipeline updates, account context, and CRM cleanup.
Free to start. No credit card required. Catalog what exists, control what's approved, and stop MCP sprawl before it compounds.
