MCPSTACK

Field reports on MCP servers — dev & devops · est. 2026

How we test

The rule

Nothing gets a case file until someone on our side actually installs it and runs it. If we haven't run it, it stays in the queue — it doesn't get published half-finished.

What we score

Every listing is rated 1–5 on five axes: setup (minutes to first tool call), reliability (did it work as documented), capability (how useful vs. alternatives), maintenance (commit activity, vendor backing), and trust & safety (auth model, permission scoping, data handling). A server that mishandles credentials caps low regardless of the rest.

Freshness

Every case file shows a last-verified date. Past 60 days without a re-check, it's marked stale. Abandoned projects aren't deleted — they're stamped abandoned, because knowing a thing is dead is still useful.

Automation, disclosed

We use AI tooling to help find candidates and draft first passes at fact sheets. No listing publishes on a draft alone — a human runs it, edits the verdict, and signs off before it goes live.

Money

Some listed tools have affiliate programs; those links are marked. We do not accept payment for a review or a score, ever. Featured/sponsored placements, if we ever run them, are visually separated from the case files and never mixed into the rankings.