MCP Servers List: Official MCP Registry Monitor
Pricing
from $1.60 / 1,000 server versions
MCP Servers List: Official MCP Registry Monitor
List and monitor MCP servers from the official Model Context Protocol registry. One row per server version: name, version, status, dates, repository, npm and PyPI packages, install command, transports, remote URLs and tool names. Find new MCP servers and tools for AI agents. Change-only monitor.
Pricing
from $1.60 / 1,000 server versions
Rating
0.0
(0)
Developer
Malik Said
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
12 hours ago
Last modified
Categories
Share
This Actor gives you a list of MCP servers from the official MCP Registry at registry.modelcontextprotocol.io. It returns one row per MCP server version. Each row has the server name, version, status, dates, repository, packages, transports and remote URLs.
Use it to find new Model Context Protocol servers, build an MCP directory or a catalog of tools for AI agents, or watch for new versions of the servers you depend on. Turn on monitor mode and schedule it. Each run then returns only new servers, new versions and status changes.
MCP registry coverage
| Item | Count on 21 October 2026 |
|---|---|
| Servers (latest version of each) | 47,547 |
| Latest versions that offer a remote endpoint (streamable-http or sse) | 30,991 |
| Latest versions that publish a package (npm, PyPI, OCI, NuGet, MCPB, Cargo) | 18,297 |
Counts come from a full test run. They grow every day.
MCP server data returned
| Field | Meaning |
|---|---|
id | Server name and version. Unique per row |
name | Server name in reverse-DNS form, for example io.github.owner/server |
namespace | The part of the name before the slash |
title, description | Display title and short description from the publisher |
version | Version of this row |
status | active, deprecated or deleted |
publishedAt, updatedAt, statusChangedAt | Registry dates, ISO 8601 |
isLatest | True when this is the newest version of the server |
websiteUrl, repositoryUrl | Links set by the publisher |
transportTypes | Every transport offered: stdio, streamable-http or sse |
packageRegistryTypes, packageIdentifiers | Package registries and package names |
packages | Each package with version, transport, runtime hint and the names of the environment variables it reads |
remoteUrls, remotes | Hosted endpoints and their transport |
installCommand | Command that starts the first package, for example npx -y name@1.0.0, uvx name==1.0.0 or docker run -i --rm image:1.0.0. Null when no standard form exists |
remoteHosts | Host names of the hosted endpoints, without duplicates |
toolNames, toolCount | Tools a hosted server lists. Only with Read tool lists on |
protocolVersion, authRequired, toolsError | MCP version the server answered with, whether it asked for a login, and why a list could not be read |
hasRemote | True when the server has at least one hosted endpoint |
changeType | Monitor mode only: new-server, new-version or status-changed |
registryUrl | API link to this exact version in the registry |
scrapedAt | When the Actor collected the row |
Empty fields are null or []. The publisher left them unset. Many servers have no title, repository or package. Remote-only servers have no packages.
How to use the MCP server list
- Run it with the default input to see the first 100 servers.
- Add filters. For example, set Transport types to
streamable-httpto list hosted servers only. - Set Maximum server versions to 0 for the whole registry.
- Turn on Monitor mode and schedule the Actor, for example once a day. The first run returns everything that matches. Later runs return only new servers, new versions and status changes.
Monitor mode remembers what it returned under the Monitor state key. Use a different key for each watch list. Later monitor runs ask the registry only for versions updated since the last complete run, so they finish fast.
| Option | Default | Meaning |
|---|---|---|
| Keywords | None | Keep servers whose name, title or description contains a keyword |
| Server name contains | None | The registry filters names by this text. Pages can be slow |
| Updated since | None | A date, a timestamp, or a period such as 7 days |
| Latest version only | On | Turn off to get every version |
| Transport types | All | stdio, streamable-http, sse |
| Package registry types | All | npm, pypi, oci, nuget, mcpb, cargo |
| Include deleted servers | Off | Also return versions the registry marked as deleted |
| Read tool lists of hosted servers | Off | Connect to each hosted (streamable-http) server and read its tool list. Slower |
| Monitor mode | Off | Return only new and changed versions |
| Monitor state key | default | Name of the monitor memory |
| Maximum server versions | 100 | Stop after this many rows. Set 0 for no limit |
| Maximum API pages | 0 (all) | Each page holds 100 rows. For quick tests |
A full scan of the latest versions read 476 pages and took about 32 minutes in our test. For a full scan (maxItems: 0), set the run memory to 512 MB in the run options. A test of the whole registry (49,061 server versions) peaked at about 180 MB, which is close to the 256 MB default. The default run timeout is 3,600 seconds. A scan of every version holds more rows and can need a longer timeout. Use monitor mode or Updated since for regular runs.
MCP registry monitor pricing
The Actor uses pay-per-event pricing.
| Event | Free plan | GOLD plan and higher |
|---|---|---|
| Run start | $0.005 | $0.005 |
| Server version | $0.002 ($2.00 per 1,000) | $0.0016 ($1.60 per 1,000) |
| Server versions in one run | Free plan | GOLD plan and higher |
|---|---|---|
| 100 | $0.205 | $0.165 |
| 1,000 | $2.005 | $1.605 |
Costs include the run start fee.
The start fee is charged once per GB of run memory, at least once. The default memory is 256 MB, so most runs pay it once. Rows skipped by your filters cost nothing. In monitor mode you pay only for new and changed rows.
Input and output example
Input from a real run on 21 October 2026:
{"nameSearch": "io.github.mc","latestOnly": true,"maxItems": 20}
The first output row from that run:
{"id": "io.github.MCFLAMINGO/local-intel@1.2.0","name": "io.github.MCFLAMINGO/local-intel","namespace": "io.github.MCFLAMINGO","title": null,"description": "Hyperlocal business intelligence for AI agents. 20 MCP tools. Florida-first, Sunbelt expansion.","version": "1.2.0","status": "active","publishedAt": "2026-04-24T05:45:55.017614Z","updatedAt": "2026-04-24T05:45:55.017614Z","isLatest": true,"repositoryUrl": "https://github.com/MCFLAMINGO/gsb-swarm","transportTypes": ["streamable-http", "sse"],"packageRegistryTypes": [],"packages": [],"remoteUrls": ["https://gsb-swarm-production.up.railway.app/api/local-intel/mcp"],"installCommand": null,"remoteHosts": ["gsb-swarm-production.up.railway.app"],"hasRemote": true,"changeType": null,"registryUrl": "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.MCFLAMINGO%2Flocal-intel/versions/1.2.0"}
MCP servers FAQ
Can I see the tools each server offers?
Yes, for hosted servers. Turn on Read tool lists of hosted servers. The Actor connects to each streamable-http endpoint, sends initialize and tools/list, and saves the tool names. It never calls a tool and sends no keys or tokens. Servers that ask for a login get authRequired: true. robots.txt is respected. Servers that only run locally (stdio packages) have no tool list here.
What is the MCP Registry?
It is the official public catalog of Model Context Protocol servers. Publishers register each server there with its packages and endpoints.
How do I get only new MCP servers?
Turn on monitor mode and schedule the Actor daily. Each run returns rows with changeType set to new-server, new-version or status-changed.
Can I list only hosted MCP servers?
Yes. Set Transport types to streamable-http or sse. Every row then has at least one remote URL.
How do I install a server from the list?
Copy installCommand. It starts the server's first package, for example npx -y name@1.0.0 for npm or uvx name==1.0.0 for PyPI. Add the server's own arguments and the environment variables listed in packages. Hosted servers have no command. Connect to a URL in remoteUrls instead.
Does it read API keys or secrets?
No. It saves only the names of the environment variables a package reads. Values, defaults and headers are never collected.
How often should I run it?
The registry asks aggregators to read it about once per hour at most. A daily schedule suits most uses.
Can AI agents use it?
Yes. An agent can search the list by keyword or transport and get flat JSON rows with install and endpoint details.
Data source and use
- All data comes from the public API of the official MCP Registry. It needs no login or key.
- The registry publishes its server metadata under CC0 1.0. This Actor has no affiliation with the MCP Registry.
- The Actor reads one page at a time.
Related Actors
- Regulator Circulars Monitor: track new circulars from the Central Bank of Jordan and the Saudi National Cybersecurity Authority.
- Drug Approvals Monitor: track new drug approvals from the FDA, EMA and Health Canada.
- Technical SEO Audit: crawl a website and find technical SEO problems.
Support
Report a problem in the Issues tab. Include the run link.