PulseMCP Server Registry API

We collect and enrich MCP-related data from all around the web and make that data available to the community via our API.

We are actively contributing to the open source Official MCP Registry, and will be releasing our sub-registry API as soon as we feel the upstream registry is stable (see prospective docs).

How we build our Directory

Our Directory is powered by:

  • Manual user submissions via pulsemcp.com/submit
  • Automated scraping/crawling processes that flow into a queue that we manually approve and curate
  • NEW: What server maintainers are publishing to the Official MCP Registry
  • Additional enrichment from various data sources that result in (early-stage) metrics like download counts, popularity, and more

Enriched Metadata & Analytics

All PulseMCP-specific metadata is namespaced under _meta["com.pulsemcp"]:

Field Type Description
estimated_downloads_all_time integer Total estimated downloads across all package registries
estimated_downloads_last_30_days integer Downloads in the last 30 days
estimated_downloads_last_7_days integer Downloads in the last 7 days
standardized_name string Human-friendly standardized name
standardized_description string Concise description of server capabilities
standardized_provider_name string Provider or organization name
standardized_provider_url string Provider or organization website URL
estimated_released_on datetime Estimated initial release date
is_official boolean Whether this is a first-party integration with an external service

Mirroring the Official Registry

We're excited for the launch of the Official MCP Registry Preview and we want to help potential consumers of the registry get up-and-running as quickly as possible. One early challenge with the new registry is that it will take some time for the most popular servers, especially those managed by major brands, to adapt their publication pipelines to push to the official registry.

So our plan is to set up "mirror" entries, exclusively available via the PulseMCP MCP Registry API, and maintain those server configurations on behalf of those popular server maintainers until they catch up and start submitting updates to the official registry themselves.

That means you can immediately start using the official Registry API shapes, integrating with all the latest and greatest MCP servers, immediately upon launch of the PulseMCP MCP Registry API (v0); no need to wait for server maintainers to start publishing first. Sign up for API updates above to be notified when we launch the mirror in October.