DEV Community

Andrei
Andrei

Posted on Originally published at serverdex.io

How to tell if an MCP server is still maintained

An MCP server is a dependency. You point your AI client at it, and from then on it sits between your agent and someone else's API. If the project behind it stops getting fixes, it breaks quietly — an API changes, an auth flow shifts, a security hole goes unpatched — and you find out the hard way. So before you wire one in, it's worth a one-minute check: is anyone still maintaining it?

Here is how to tell, what the data across the directory actually shows, and the handful of well-known servers that are already archived.

The signals that tell you

You don't need to read the code. A few repository signals, all visible on the server's GitHub page (and surfaced on its Serverdex listing), give you the answer:

  • Last commit. The single best signal. A repo pushed in the last few weeks is alive; one untouched for a year is effectively done, no matter how many stars it has.
  • Archived flag. If the owner has archived the repo, GitHub marks it read-only. That is a deliberate "this is finished" — the strongest signal of all.
  • Open issues and their age. A pile of open issues with no maintainer replies in months means questions go unanswered.
  • Releases. A recent tagged release says the maintainer still ships; years since the last one is a warning.
  • Stars are not maintenance. A popular server can still be abandoned. Airweave's search server has over 6,500 stars and is archived. Treat stars as reputation, not upkeep.

What the data says: most MCP servers are fresh

MCP is young, and it shows. Across the 12,129 MCP server repositories Serverdex has read on GitHub (as of 15 November 2026):

Status Share
Active — updated in the last 90 days 92%
Quiet — last commit 3–12 months ago 7%
Dormant — no commit in over a year under 0.1%
Archived on GitHub under 1%

So the "graveyard of abandoned MCP servers" is mostly a myth today — nine in ten have been touched in the last three months. The real job isn't wading through dead projects; it's spotting the exceptions before you build on one. (For the wider picture — growth, remote vs local, languages and packages — see the State of MCP report.)

The notable archived ones

A few servers people still find and install are already archived — read-only, no further fixes:

  • Airweave Search — 6,545 stars, archived. The most-starred archived MCP server in the directory.
  • Storybook MCP Addon — 272 stars, archived.

If you depend on one of these, pin your version and plan a migration; nothing more is coming.

How a directory can surface it

Every server page on Serverdex carries a maintenance badge next to the name, worked out from the repository's own signals:

  • Active — committed to in the last ~3 months.
  • Quiet — gone 3–12 months without a commit.
  • Dormant — over a year since the last commit.
  • Archived — the repo is archived on GitHub.

It is shown only when the repository has been read, and the archived flag always wins. One honest word, so you don't have to decode a raw date.

Before you commit to a server

Open its page, glance at the badge and the last-commit date, skim the open issues, and check for a recent release. A minute of this saves a broken integration later. When you're choosing between options, browse maintained servers by category — and if you maintain one yourself, claim your listing so its page shows you're active.

Top comments (2)

Collapse
 
x1y1co profile image
X1Y1 •

The repo view and the config view tell different stories. When we ran 10,659 public MCP config files from GitHub through our checker, 941 (9%) still used a package npm marks deprecated, and 819 of those were the original reference servers archived in May 2025. server-github from that set alone appeared 580 times, even though GitHub ships its own server now. So archived repos are under 1% of what's published, but a much bigger share of what people actually run, because copied configs and tutorials outlive the repo. Showing npm's deprecated flag next to the GitHub badge would catch those at install time.

Collapse
 
paul_irolla_6b5ae261d0224 profile image
Paul Irolla •

Maintenance is one check. The other is cost: a server's tool definitions go out with every request, used or not, so a server with tools you never call is paid for on each turn of every session. Trim it before you judge the project.