MCP Server Registry Scraper — Official MCP Registry + Smithery avatar

MCP Server Registry Scraper — Official MCP Registry + Smithery

Pricing

from $1.60 / 1,000 entries

Go to Apify Store
MCP Server Registry Scraper — Official MCP Registry + Smithery

MCP Server Registry Scraper — Official MCP Registry + Smithery

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.

Pricing

from $1.60 / 1,000 entries

Rating

0.0

(0)

Developer

Northbell

Northbell

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

1

Monthly active users

42 minutes ago

Last modified

Share

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.

Try it now — the input is already filled in. Press Start: 100 Smithery servers with their use counts in about 40 seconds, for about $0.21.

nameserverIdtransportsuseCount
Brave Searchbraveremote87579
Gmailgmailremote57738
OneSignalonesignal/onesignalremote22491

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 }.

{
"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": []
}

Get only what changed, every morning (3 steps)

  1. Open this Actor in Apify Console, set What to return to Only what is new or changed since the last run, and click Save as a new task.
  2. On the task, add a Schedule — for example daily at 07:00.
  3. Open the task's Integrations tab and connect Slack, email, Google Sheets (or Zapier / Make / a webhook). Each morning you get only the new, changed and removed entries.

You pay only for the rows returned plus $0.01 per run, so a quiet day costs about a cent.

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.

**Measured, not estimated:** about **$0.0073 per 1,000 entries** of Apify platform usage at 512 MB (our running cost — included in the price, nothing on top) (1000 entries in 152 s, 2026-09-27).

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 · Lever · Ashby · Workday · AI companies.