# MCP Server Registry Exporter (`agentdataco/mcp-registry-exporter`) Actor

Export every published Model Context Protocol (MCP) server from the official registry as clean JSON. Filter by status, name and latest version.

- **URL**: https://apify.com/agentdataco/mcp-registry-exporter.md
- **Developed by:** [Agent Data Co](https://apify.com/agentdataco) (community)
- **Categories:** AI, Developer tools, MCP servers
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## 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:

```json
{
  "status": "active",
  "latestOnly": true,
  "maxItems": 200
}
```

### Output

Each dataset item looks like this:

```json
{
  "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](https://agentdataco.com) 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-servers` and `/api/v1/mcp-servers/history?entity=...` ([docs](https://agentdataco.com/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

# Actor input Schema

## `status` (type: `string`):

Official registry status. Empty = all.

## `nameContains` (type: `string`):

Name contains.

## `latestOnly` (type: `boolean`):

Latest version only.

## `maxItems` (type: `integer`):

Max results.

## `registryBase` (type: `string`):

Registry base URL.

## `allowEmpty` (type: `boolean`):

Allow empty results (tests).

## `search` (type: `string`):

Optional registry search term (server-side name search).

## `maxPages` (type: `integer`):

Safety cap on pages of 100.

## Actor input object example

```json
{
  "status": "active",
  "latestOnly": true,
  "maxItems": 500,
  "registryBase": "https://registry.modelcontextprotocol.io",
  "allowEmpty": false,
  "maxPages": 200
}
```

# Actor output Schema

## `results` (type: `string`):

Dataset items produced by this run (one item per charged result).

## `runSummary` (type: `string`):

Count of results, duration and whether the charge limit was hit.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("agentdataco/mcp-registry-exporter").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("agentdataco/mcp-registry-exporter").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call agentdataco/mcp-registry-exporter --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,agentdataco/mcp-registry-exporter"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/Mmd4EHrig3b4V7e91/builds/uwlqonmbuzYlf7kZW/openapi.json