MCPSkill
MCP vs SkillMCP Markets
Examples

MCP and Skill Market

How to tell a genuinely useful MCP server or Agent Skill from a popular but abandoned one, and where to browse a catalog that keeps itself current.

Why a catalog matters

Installing an MCP server or an Agent Skill is easy. Choosing a good one is not. Most discovery still happens through long "awesome" lists where a project with ten thousand stars sits next to one that was abandoned two years ago, and nothing on the page tells you which is which.

A useful catalog does more than list names. It sorts projects, keeps metadata fresh, and gives you enough context to judge whether a server or Skill deserves a place in your agent.

How to judge an MCP server

Before you connect anything to a client, check four things.

Maintenance healthWhen was the last commit, and are issues actually answered? An unmaintained server is a security liability, not a shortcut.
Community adoptionStars alone are a weak signal. Look for real usage: forks, downstream mentions, third-party integrations.
DocumentationDoes it explain the tool schema, the credentials it needs, and how it fails? If you cannot tell what a tool returns, the agent cannot use it well either.
Permission boundaryDoes it ask for read-only access or full write access? Least privilege should be visible before installation, not discovered afterwards.

How to judge an Agent Skill

Skills ship as plain files, so the quality question is different from a server.

Description clarityThe description is what the agent sees before activation. If it is vague the Skill never loads; if it is too broad it fires on unrelated work.
Activation boundaryDoes the Skill say when it should and should not be used? A clear boundary matters more than a long document.
ComposabilityCan it run alongside your existing tools without conflicting? A Skill that assumes it owns the whole workflow is hard to reuse.
Bundled assetsScripts and references are a feature only when they earn their place. Check that any bundled automation is something you would run yourself.

What catalogs actually contain

Discovery is unevenly distributed. Developer tooling dominates the server side, while Skills cluster around research and review work. Knowing the shape of the ecosystem keeps you from searching in the wrong place.

TypeCategoryRelative volume
MCP serverDeveloper toolsBy far the largest group
MCP serverAPI developmentSmall but steady
MCP serverBrowser automationSmall and growing
MCP serverProductivity workflow, database management, communicationNiche
Agent SkillResearchLargest Skill group
Agent SkillCode reviewSecond largest
Agent SkillWriting, data analysisSparse
Practical takeaway

If you need a server for something unusual, expect few options and read them carefully. If you need a research or code review Skill, you will have real choice.

How to read rankings and trending lists

Every catalog ranks differently, and any ranking you see is a proxy rather than a verdict. Three things are worth checking before you trust a placement.

1
What is being measured

Adoption, maintenance activity, and raw popularity are different metrics. A list sorted by stars answers a different question than one sorted by health.

2
How fresh the data is

A catalog that refreshes from source repositories reflects a project's current state. A hand-edited list decays quietly and keeps recommending dead projects.

3
Whether the order is explained

If a ranking never states what it ranks by, treat it as a browsing starting point rather than a recommendation.

Where to browse a maintained catalog

MCP Markets is a directory for MCP servers and Agent Skills that we work alongside. It tracks several thousand servers and Skills, refreshes its inventory from source repositories on an hourly basis, and ranks servers by community adoption and maintenance health rather than by raw star count.

It is organized the way the table above suggests: developer tools make up the bulk of the server side, while research and code review lead the Skill side. The catalog also publishes focused ranking pages, so you can start from the client you already use instead of browsing everything.

Start here

If you want a single entry point, open MCP Markets, pick your client or category, and read the maintenance signals before installing anything.

Getting your own project listed

If you maintain a server or a Skill, a catalog listing is one of the cheapest ways to be found by people who are already looking for exactly what you built. Most directories accept submissions for free and ask for a repository link rather than a paid placement.

Before submitting, make sure the repository has a readable description, a working install path, and a clear statement of which permissions the project needs. Those three things are what both catalogs and their readers screen for.