MCP Server Registry Scraper — Official MCP Registry + Smithery
Pricing
from $1.60 / 1,000 entries
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.
You can access the MCP Server Registry Scraper — Official MCP Registry + Smithery programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in API & Integrations in Apify Console.
{ "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,northbell/mcp-server-registry-scraper" } }}The configuration above connects to the hosted Apify MCP server with the MCP Server Registry — Official + Smithery, New Servers Actor already loaded. It uses OAuth, so your client opens a browser window to sign you in to Apify on first use. No API token is needed. Clients without OAuth support can authenticate with an Authorization: Bearer header carrying an API token from API & Integrations in Apify Console.
Get a ready-to-use configuration for your MCP client with the MCP Server Registry — Official + Smithery, New Servers Actor preconfigured at https://mcp.apify.com/?tools=fetch-actor-details,northbell/mcp-server-registry-scraper.
You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other MCP client of your choice.
If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.