MCP SERVER DISCOVERY
Search the official MCP Registry
without maintaining custom ingestion
Search the official Model Context Protocol Registry and export server names, descriptions, versions, lifecycle status, repositories, and update dates.
40
Ahrefs Global Searches / Mo
Official
Registry Source
API
Dataset Access
$0.002
Per Stored Result
Ahrefs Keywords Explorer, 23 Jul 2026 — global monthly volume for “mcp registry api”.
DIRECT ANSWER
What is Official MCP Registry API?
Official MCP Registry API is a pay-per-result Apify Actor that searches the official Model Context Protocol Registry and exports normalized server records. It is intended for server discovery, internal catalogs, and scheduled registry snapshots; it does not scrape third-party directories or execute listed servers.
USE CASES
Where it fits
MCP server discovery
Search official Registry records by server name, namespace, or description and export a clean shortlist.
Internal MCP catalog
Feed normalized official records into an internal developer portal, spreadsheet, or governance workflow.
Scheduled registry snapshots
Collect the same query set on a schedule and compare datasets downstream for lifecycle or version changes.
OUTPUT
Data you can export
WORKFLOW
How it works
01
Enter server queries
Add up to 20 server names, namespaces, or search terms to match against official Registry records.
02
Normalize official records
The Actor reads the official Registry API and maps matching records into a stable dataset contract.
03
Export or connect
Download the dataset or connect it to another catalog, agent workflow, or scheduled webhook.
COMPARISON
Why use an actor?
| Feature | Official MCP Registry API | Manual Registry browsing | Third-party MCP directory scraper |
|---|---|---|---|
| Official Registry source | Yes | Yes | No |
| Structured API export | Yes | No | Usually |
| Third-party directory data | No | No | Yes |
| Pricing | $0.002/result | Your time | Varies |
FAQ
Questions buyers ask
Is this a multi-registry MCP scraper?
No. Despite the legacy Actor slug, the runtime reads only the official Model Context Protocol Registry.
Does it execute or security-scan MCP servers?
No. It exports published Registry metadata and does not connect to, run, or score listed servers.
Can I use it for an internal MCP catalog?
Yes. The normalized dataset can feed a developer portal, spreadsheet, database, or governance review workflow.
What does a result cost?
The list price is $0.002 per successfully stored Registry record on the Apify Free plan, with lower per-result prices on paid Apify plans. Empty, canary, and failed rows are not charged.
Is this Actor affiliated with the Model Context Protocol project?
No. It is an independent Apify Actor that reads the official public Registry API. Model Context Protocol names and marks belong to their respective owners.
RELATED
Related tools
Run Official MCP Registry API on Apify
Pay $0.002 per successfully stored result on the Apify Free plan, with lower per-result prices on paid Apify plans.
Open Apify Actor→