About mcpnav
mcpnav tracks 31,766 MCP (Model Context Protocol) server listings merged from three sources. Only 5,954 of those get their own page on this site — see "Which servers get a page" below.
Data sources
- Official MCP Registry (
registry.modelcontextprotocol.io) — data comes from the Official MCP Registry, which publishes it under CC0 (public domain). Entries are self-published by server authors; a listing here does not imply endorsement by the Registry, Anthropic or the Model Context Protocol project. - punkpeye/awesome-mcp-servers, MIT License. Copyright © 2024 Frank Fiegel (frank@glama.ai)
- wong2/awesome-mcp-servers, MIT License. Copyright (c) 2024 wong2
Which servers get a page
A server is not archived, and gets a page here if at least one of the following is true:
- it's listed in punkpeye/awesome-mcp-servers or wong2/awesome-mcp-servers, or
- its GitHub repository has 10 or more stars, or
- it's flagged official by one of the source lists.
This keeps low-signal, unstarred, self-published Registry entries out of the index while still counting them in the total above. The threshold may change in a future update.
How this site updates
Data is refreshed manually, not on a live feed. This snapshot was fetched 2026-09-24. New Registry publications, README changes and star counts appear here after the next manual refresh, not immediately.
How the remote reachability badges work
Servers with a hosted remote endpoint (Registry remotes entries) are checked
with exactly one MCP initialize request per URL. We never send the endpoint's
own declared authentication headers, so a 401/403 response is recorded as "Requires auth,"
not treated as a failure. A badge only ever reflects the result at the moment it was
checked — it can change between refreshes, and mcpnav does not guarantee an endpoint
is reachable right now just because a badge says so.
As of 2026-09-24, 1,045 remote endpoints were checked: 491 reachable, 411 requiring auth, 27 unreachable, 64 returning an HTTP error, and 4 that responded but not as an MCP endpoint.
Not affiliated
mcpnav is an independent directory. It is not affiliated with, endorsed by, or a partner of Anthropic or the Model Context Protocol project.
Frequently asked questions
Where does mcpnav's data come from?
The data comes from the Official MCP Registry (registry.modelcontextprotocol.io), whose terms dedicate published server metadata to the public domain under CC0 1.0, plus two MIT-licensed curated lists: punkpeye/awesome-mcp-servers and wong2/awesome-mcp-servers. Repository metadata such as stars and archive status is read from GitHub. mcpnav does not copy README files and does not scrape other directory sites.
Why doesn't every server in the Registry have a page here?
The Registry is self-published and permissive by design; its maintainers say consumers should assume minimal-to-no moderation. mcpnav generates a page only for records that are not archived on GitHub and that either appear in one of the two curated lists, have at least 10 GitHub stars, or carry an official flag from those lists. The remaining records stay in the dataset but are not rendered.
How often is the data updated?
Refreshes are currently run manually. Each page's data is taken from the most recent fetch, and the sitemap's lastmod reflects that fetch date. A daily automated refresh using the Registry's updated_since filter is planned; the Registry's own guidance for aggregators is to pull on a regular but infrequent schedule.
Is mcpnav affiliated with Anthropic or the Model Context Protocol project?
No. mcpnav is an independent directory. It consumes public data from the Official MCP Registry and two community-maintained lists, and it is not operated by, endorsed by, or affiliated with Anthropic, the MCP project, or the Registry maintainers. Servers appear here because their metadata is public, not because anyone reviewed them.