# MCP Server Registry Scraper — Official + Smithery, New Servers (`northbell/mcp-server-registry-scraper`) Actor

Every MCP server in the official Model Context Protocol registry and on Smithery — name, description, version, transports, remote URLs, packages, use count — plus exactly which servers are new, removed or updated since your last run.

- **URL**: https://apify.com/northbell/mcp-server-registry-scraper.md
- **Developed by:** [Northbell](https://apify.com/northbell) (community)
- **Categories:** AI, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.60 / 1,000 entries

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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 Scraper

Every MCP (Model Context Protocol) server listed in the **official MCP registry** and on **Smithery** — over 16,000 entries in a test run — with name, description, version, transport (streamable HTTP / remote), remote URLs, packages, repository, and Smithery use counts.

Run it on a schedule and it tells you **exactly what changed since the last run**: new servers, removed servers, version bumps, and how many uses each Smithery server gained (`useCountSinceLastRun`).

### Use it for

- **Finding MCP servers** for your agent by keyword, without clicking through two directories
- **Tracking the MCP ecosystem** — what launches each day, what is growing fastest
- **Lead lists** of companies shipping MCP servers

### Notes

- The official registry keeps one row per version; only the latest version of each server is returned.
- Smithery `useCount` growth is reported as a number (`useCountSinceLastRun`), not as a "change", so a daily diff is not flooded by every popular server.

### Example output

One real row from a test run (long text shortened here with …). On later runs `changes` lists what moved, as `{ field, from, to }`.

```json
{
  "type": "item",
  "source": "mcp",
  "registry": "smithery",
  "serverId": "brave",
  "name": "Brave Search",
  "description": "Search the web with Brave's independent index — web, news, images, and videos. Bring your own subscription token from the [Brave Search API dashboard](https://a…",
  "version": null,
  "status": "active",
  "remoteUrls": [],
  "transports": [
    "remote"
  ],
  "packages": [],
  "repository": null,
  "useCount": 87579,
  "verified": true,
  "publishedAt": "2025-09-05T18:07:47.018Z",
  "updatedAt": null,
  "homepage": "https://brave.com/search/api/",
  "url": "https://smithery.ai/server/brave",
  "useCountSinceLastRun": null,
  "isNew": null,
  "changes": []
}
```

### Pricing

**$2.00 per 1,000 entries**, plus $0.01 per run. Removed-entry rows and errors are free. Use **Max entries** and **Only what is new or changed** to keep a scheduled run cheap.

### For AI agents

Rows have `type`: `item`, `removed` or `error`. `isNew: null` means "no previous run to compare with", not "old". `changes` is a list of `{ field, from, to }`.

### More from northbell

Job boards with exact new/closed tracking: [Greenhouse](https://apify.com/northbell/greenhouse-jobs-scraper) · [Lever](https://apify.com/northbell/lever-jobs-scraper) · [Ashby](https://apify.com/northbell/ashby-jobs-scraper) · [Workday](https://apify.com/northbell/workday-jobs-scraper) · [AI companies](https://apify.com/northbell/ai-jobs-scraper).

# Actor input Schema

## `registries` (type: `array`):

Leave empty for both. The official registry takes about 3 minutes for all of it.

## `keywords` (type: `string`):

Comma-separated. Keep only entries whose name, id or description contains any of these. The new/changed/removed comparison still uses the whole catalog.

## `output` (type: `string`):

Schedule this Actor and pick "Only what is new or changed" to get a cheap daily diff. The first run always returns everything (there is nothing to compare with yet).

## `trackChanges` (type: `boolean`):

Keeps the last catalog so the next run can report new, changed and removed entries exactly.

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

Caps what you are charged for. The comparison still uses the full catalog. $2.00 per 1,000 entries.

## Actor input object example

```json
{
  "registries": [
    "smithery"
  ],
  "output": "all",
  "trackChanges": true,
  "maxItems": 1000
}
```

# Actor output Schema

## `all` (type: `string`):

No description

## `items` (type: `string`):

No description

# 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 = {
    "registries": [
        "smithery"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("northbell/mcp-server-registry-scraper").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 = { "registries": ["smithery"] }

# Run the Actor and wait for it to finish
run = client.actor("northbell/mcp-server-registry-scraper").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 '{
  "registries": [
    "smithery"
  ]
}' |
apify call northbell/mcp-server-registry-scraper --silent --output-dataset

```

## MCP server setup

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

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/OEQoQ8Av99WUmIvax/builds/wQRf75GDhD1Mz1L0y/openapi.json