What you get
- A severity-weighted score across the same categories the report and mcpscore.dev show — Protocol, Primitives (tools, prompts, resources, resource templates, pagination), and Security & Auth — deterministic, no API keys, CI-ready.
- A readiness score for the latest spec revision (2026-07-28, stateless lifecycle) — reported on its own axis. For legacy servers it informs without punishing; servers already on the modern lifecycle have these points counted in the main score (see promotion).
- Actionable messages — every failed check says what to fix, and every rule is anchored to the spec (see the methodology).
Quick start
Auditing auth-gated servers
Many production MCP servers require OAuth 2.x. With a credential (--token, --header, or the browser --oauth flow), mcpscore audits behind
the gate like any client; without one, the server still gets a partial
audit of its observable surface — auth posture, TLS, and transport — marked
partial and not comparable to a full audit. Credential values are never
logged or written to the report. The
Authenticated Servers guide walks through every
flavor, including a worked example against GitHub’s Copilot MCP server.
Example output tail (a full audit):
Learn more
Scoring Methodology
How the score works, and why you can trust it
Rules Reference
Every rule, its severity, and when it applies
Authenticated Servers
Audit behind OAuth and API keys — or score the observable surface
Smoke Mode
Verify after every change that your server still works — its tools actually run
GitHub Action
Gate pull requests on quality, with a report comment
Score Badge
A live badge for your README that tracks your latest score
Package Audits
Score a published npm or PyPI package without running it
Source
mcp-box/mcpscore — issues and contributing
PyPI
uv tool install mcpscore · pip install mcpscore