MCP Market (mcpmarket.com): What It Is and How to Use It

MCP Market is a directory at mcpmarket.com that lists MCP servers, MCP clients and agent skills. It is run by Sitka Labs, a company, and it is not the official MCP registry. Listing is free with a wait of weeks or $29 for a fast listing. It helps you discover servers, but it does not vouch for them, so check each repo before you install. We checked it on 31 October 2026.

Quick facts

What it is, in plain terms

Think of it as a shop window with a search box. Someone submits a link to a GitHub repo or a remote server. The site shows a tile with a name, a short description, a category and a number that looks like a GitHub star count. You click through to the listing, then to the source.

That is useful. MCP servers are scattered across GitHub, npm, vendor docs and a few registries, and a single place with categories saves time. The home page groups them as Official, Featured, Top, Latest, plus clients and agent skills.

It is also a business. The site sells listing upgrades, a skill marketplace, a hub product and advertising (its footer links to "Advertise with us" and "Affiliates"). None of that is a problem. It does shape how you read a tile.

What is on the site

Servers

The server directory is the core. Each tile names the server, gives a one-line description, a category or two and a count. Categories on the site include Developer Tools, Data Science and ML, API Development, Productivity and Workflow, Analytics and Monitoring, Security and Testing, Web Scraping and Data Collection, Deployment and DevOps, Content Management, Database Management, Collaboration Tools, Cloud Infrastructure, E-commerce Solutions, Marketing Automation, Design Tools, Browser Automation, Social Media Management, Game Development, Mobile Development, Learning and Documentation, and Other.

An "Official" set groups servers from the vendors themselves. When we looked it included Firecrawl, ElevenLabs, Magic, Browserbase, Exa and Tavily. We cover several of these on this site: Firecrawl MCP, Exa MCP, Tavily MCP and Browserbase MCP.

Clients

A smaller list of MCP clients such as Zed, Cline, Cherry Studio, LibreChat, Goose and 5ire. For how the main coding agents handle MCP, our MCP clients page is the better guide.

Agent skills

The site also lists agent skills, which are folders with a SKILL.md. Our Agent skills page explains the format and where each agent loads them.

The leaderboard

The Top 100 page ranks servers "by GitHub stars", per its own text. Stars measure attention, not quality or safety. A server with a large number may be a popular workflow or prompt collection rather than a server you would connect to your database.

How listing works and what it costs

The submit page says you submit the GitHub repository, or a remote MCP URL, and the site reviews it for inclusion. It offers two routes.

Two things to take from this.

First, a badge can be bought. The page offers an "Official badge on your tile + page" for the $29 route. The free queue is described as having no Official badge, and the site also has a separate Official MCP Servers section. We found no statement of whether the two are the same thing. Until that is clear, do not read it as an endorsement from the vendor or from the MCP project.

Second, a fast listing is not a review. Paying gets you listed sooner. Nothing on the page says paid listings get a security audit. We found no statement that any listing is audited.

Selling skills and the Hub

Two parts of the site go beyond a directory.

Sell skills. A seller page invites you to list agent skills as paid items, set your own price, publish versions, sync from GitHub or upload a SKILL.md, and share a storefront link. It says buyers get the latest version. The page includes sample numbers in its mock-up, which we do not treat as real figures.

Hub. The Hub page describes version control for skills and MCPs: create or import a skill, draft, publish and roll back, then "sync through the plugin" so updates reach your agents. It also describes bundling tools into toolkits for a team. The Hub page says the plugin works with Claude Code, Claude Desktop, Codex, Cursor and any MCP-enabled client. We did not install it, so we cannot say what access it asks for.

If you are a skill author, the sell page is a distribution channel. If you are a buyer, remember that a paid skill is still instructions and code that run in your agent, and apply the same review you would give a free one.

What we noticed on the site

These are observations from the pages as we fetched them. They show why a listing is a lead, not a verdict.

1. A listing can point at an archived project. The home page's Featured set has a WordPress server described as exposing WordPress through MCP, with a count of 947. That number matches the star count of Automattic/wordpress-mcp, which is archived on GitHub and points users to WordPress/mcp-adapter. We cover the maintained option on our WordPress MCP page.
2. Counts can lag. The Firecrawl tile showed 4.2k. The GitHub repo showed 7,729 stars when we checked. The difference may be a stale cache. It tells you the number is not live.
3. The server count is a marketing number. 50,999 on one page and "35K+" on another. Neither is a count of servers you would want to run.
4. Top of the leaderboard is not a safe list. The top entries are very large repos whose descriptions read like development workflows and tools, not simple servers.

None of this means the site is bad. It means the usual rule holds: read the repo.

How to vet a server you find there

A five-minute habit that works for any directory:

1. Open the source. Follow the tile to the GitHub repo or vendor docs. If there is no repo and no vendor, stop.
2. Check the repo state. Look for an "archived" banner, the last commit date, the latest release and open issues.
3. Check the licence. A missing licence file means you have no stated right to use it.
4. Read the tool list. Find the tools it exposes. A "read documents" server that also has "run shell command" is not what it says.
5. Read the auth. Does it ask for a broad token? Can you scope it to read-only?
6. Check who runs it. An official vendor server and a one-person hobby server carry different risks.
7. Try it with nothing valuable attached. Use a throwaway token and a test project first.

This sits on top of the usual MCP security notes: a server runs with your access, and tool descriptions are text a model reads, so a hostile server can try to steer it. Keep a short allow list of servers, and review tool lists after updates.

From a tile to a working install

A directory tile is only the first step. Here is the path we would follow for any server found on MCP Market.

1. Find the install line at the source. The repo README or vendor docs hold the real command. A tile may summarise it, but the README is the document the author maintains.
2. Match it to your agent. Most servers document a stdio line (a command your agent starts) or a remote URL. Our MCP clients page shows how Claude Code, Codex, Antigravity, Cursor and OpenCode each name those fields, so you can translate a README line for the agent you use.
3. Pin what you can. Use a version in the command where the server allows it, so an update does not change your tools without you knowing.
4. Scope the credentials. Make a token with only the permissions the job needs. Where the server has a read-only mode, turn it on.
5. List the tools after install. Ask the agent what tools the server added and compare that with the README. A difference is a reason to stop.
6. Remove what you do not use. An unused server is attack surface and context cost with no benefit.

For example, if a tile for a search server catches your eye, the vendor docs may offer a hosted endpoint, an npm command and a container image. The hosted one means you trust the vendor with your queries. The npm one runs code on your machine. The container one adds a boundary. Our write-ups of Firecrawl MCP and Docker MCP show how those three routes differ in practice.

Reading a tile like an editor

A tile gives you four things, and each has a limit.

The best signal on any listing is the thing it links to. A vendor-run repo with recent commits, a licence file and a clear security note says more than any badge on a directory.

Where it fits among other directories

Our MCP marketplace page compares the main ones in detail, and the MCP servers hub lists servers we have written up. For Docker's route, see Docker MCP.

Who should use it

• Developers browsing for ideas get a quick look at what exists in a category.
• Teams choosing a server should use it to build a shortlist, then verify each item at the source.
• Server authors can use the free queue, or pay if a fast listing matters for a launch.
• Skill authors can look at the sell page, with the usual care about pricing and support.
• Anyone who wants a vetted list should prefer vendor docs and the official registry.

Privacy and data

The privacy policy says Sitka Labs collects account information such as email and optional name, billing information and usage data. It names the site's APIs and related services as part of the "Service". Read the full policy before you create an account or connect the plugin. We did not read every clause.

If you submit a server, you provide a repo URL and an email address, and the site says it will email you when the listing is live.

Our take

We did not use the Hub or the plugin for this page. This comes from the public pages we fetched.

MCP Market is a decent place to browse. The categories are sensible and a quick scan shows you what kinds of servers exist. As a discovery tool it does its job.

As a source of trust it does not. A paid badge, counts that lag, a featured entry that points to an archived repo and a leaderboard that ranks by stars are all reasons to treat every tile as a lead.

Use it to build a list. Then do the five-minute check at the source. If you want a smaller, vetted route, start from a vendor's own docs or the official registry.

Quick checklist

1. Use the site to find candidates, not to decide.
2. Open the source repo or vendor page for each one.
3. Reject archived repos unless you can name the maintained replacement.
4. Check licence, last release and open issues.
5. Read the tool list and the token scopes.
6. Try with a throwaway credential first.
7. Do not read a badge as an audit.

Frequently asked questions

What is MCP Market?

A website, mcpmarket.com, that lists MCP servers, clients and agent skills, with a leaderboard and a paid listing option. Sitka Labs operates it.

Is MCP Market the official MCP registry?

No. The official registry is at registry.modelcontextprotocol.io.

How much does it cost to list a server?

The free queue has a stated average wait of 4 to 6 weeks. A one-time $29 fast listing goes live within 24 hours and adds a badge and a Try Now link.

Can I trust the listings?

Treat them as leads. Check the source repo, its licence and its state before you install anything.

Does it host the servers?

The listings point to GitHub repositories or remote endpoints. We found no statement that it hosts or audits the code.