MCP Toplist vs MCPfinder - MCP Server Discovery
MCP Toplist is an MCP server published by mcptoplist.com. Marketplaces we read that list it: 1 (Official MCP Registry). MCPfinder - MCP Server Discovery is an MCP server published by mcpfinder.dev. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-27. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  MCP Toplist |  MCPfinder - MCP Server Discovery |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.2 No figure published Not marked · First seen |
Listed Version: 1.5.0 Downloads/month (npm): 1 129 Downloads/week (npm): 198 Forks (GitHub): 4 Stars (GitHub): 13 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 2.0.1 Downloads/month (npm): 1 129 Downloads/week (npm): 198 Forks (GitHub): 4 Stars (GitHub): 13 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | MCP Toplist | MCPfinder - MCP Server Discovery |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 13 |
| Forks (GitHub) (differs) | No figure on GitHub | 4 |
| Last release (differs) | 2026-10-13 (worse) | 2026-10-20 (better) |
| Where it runs (differs) | Remote server (mcptoplist.com/mcp) | On your machine (@mcpfinder/server) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Not stated | AGPL-3.0-or-later |
| Repository (differs) | Not stated | github.com/mcpfinder/mcpfinder |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 3 days ago | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
MCP Toplist
Search 100,000+ MCP servers ranked by real adoption data to find the right one for any task.
MCPfinder - MCP Server Discovery
Your AI discovers and installs MCP servers across Official Registry, Glama, and Smithery.
How to run each
MCP Toplist As a remote MCP server
claude mcp add --transport http mcptoplist https://mcptoplist.com/mcpMCPfinder - MCP Server Discovery As a local MCP server: npm package
claude mcp add --transport stdio mcpfinder-mcp-server-discovery -- npx -y @mcpfinder/serverCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only MCP Toplist has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of MCPfinder - MCP Server Discovery nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: MCP Toplist · What it can do: MCPfinder - MCP Server Discovery · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.