MCP Server Registry Exporter
Pricing
Pay per event
MCP Server Registry Exporter
Export every published Model Context Protocol (MCP) server from the official registry as clean JSON. Filter by status, name and latest version.
Pricing
Pay per event
Rating
0.0
(0)
Developer
Agent Data Co
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
an hour ago
Last modified
Categories
Share
MCP Server Registry Exporter — Full Catalog Dump
Export every published Model Context Protocol (MCP) server from the official registry as clean JSON. Filter by status, name and latest version.
What does MCP Registry Exporter do?
Pulls the official MCP registry (registry.modelcontextprotocol.io) via its public HTTP API and writes one dataset row per server version (name, title, description, remotes, packages, status, publish dates). Ideal for MCP directories, agent marketplaces and researchers.
Why use it?
- Official registry API — no scraping, no auth
- Cursor-based pagination for full dumps
- Filter by status / name / latest-only
- Fail-loudly empty-result guard
Data source
Official MCP Registry API GET /v0/servers at https://registry.modelcontextprotocol.io (public).
Input
- status: active | deprecated | deleted | empty
- nameContains: Substring filter
- latestOnly: Only latest versions
- maxItems: Cap
- registryBase: Override base URL
Example input:
{"status": "active","latestOnly": true,"maxItems": 200}
Output
Each dataset item looks like this:
{"name": "io.github.modelcontextprotocol/server-github","title": "GitHub","version": "1.0.0","status": "active","remotes": []}
Export as JSON, CSV, Excel or HTML, or pull via the Apify API, webhooks, Make, Zapier, n8n or the Apify MCP server.
How much does it cost?
Pay per event: $0.001 per run + $0.001 per result (≈ $1.00 per 1,000 results). You are never charged for results on a failed run: if no data is found, the run fails loudly with an explanation instead of returning an empty "success".
Use cases
- MCP directories / marketplaces syncing catalog
- Agent builders discovering tools
- Researchers measuring MCP ecosystem growth
- Change-detection pipelines (diff two runs)
Scheduling & monitoring
Schedule it daily or weekly in Apify Console and connect a webhook/Slack/email integration to get new items automatically.
FAQ
Is this legal? It uses the official public MCP Registry HTTP API. Server metadata is published by authors to the registry.. No personal data is collected.
Something broke? Open an issue on the Issues tab; the actor is tested daily.
Built and maintained by Agent Data Co — reliable AI-ecosystem data for agents and analysts.
Need history and trends? Use the Agent Data Co API
This Actor gives you a fresh snapshot each run. Agent Data Co runs the same collection every day and keeps an append-only archive, so you can get daily history per entity, 1d/7d/30d top movers and change events without scheduling runs or storing results yourself:
- REST:
GET https://agentdataco.com/api/v1/mcp-serversand/api/v1/mcp-servers/history?entity=...(docs) - MCP for AI agents:
https://agentdataco.com/mcp(Streamable HTTP; free sample tools work without a key) - Free sample, no key: https://agentdataco.com/api/v1/sample?name=mcp-servers
- Public trend pages: https://agentdataco.com/trends · example: https://agentdataco.com/mcp/co.pipeboard/snap-ads-mcp
- Plans: Starter $19/mo (latest data + 30-day history), Pro $49/mo (full archive, trends, priority watchlist): https://agentdataco.com/#pricing