mcpscore — MCP server audit

Version updated for https://github.com/mcp-box/mcpscore-action to version v1.

  • This action is used across all versions by ? repositories.

Action Type

This is a Composite action.

Go to the GitHub Marketplace to find the latest changes.

What’s Changed

First release of the mcpscore GitHub Action — Lighthouse for MCP in your CI.

Audit an MCP server on every pull request, fail the build when quality drops below a threshold you set, and get the report as a PR comment.

- uses: mcp-box/mcpscore-action@v1
  with:
    target: https://your-server.example/mcp
    min-score: 80

What it does

  • Score gate — fail the job when the main score falls below min-score (a percentage).
  • Readiness gate — optionally require readiness for the upcoming MCP 2026-07-28 spec via min-readiness (reported separately, never mixed into the main score).
  • PR comment — posts one report comment and updates it in place on re-runs: score, a pass/fail breakdown by severity, spec version and era, and every failed check by rule_id.
  • Job summary + outputs — the same report in the run summary, the raw JSON on disk, and every number exposed as a step output (score, percentage, era, readiness-*, …).
  • Deterministic — no API keys, no LLM calls; the same server state always produces the same result, in seconds.

Works against remote servers (Streamable HTTP / SSE) and local .py / .js servers.

Links:

Full changelog: https://github.com/mcp-box/mcpscore-action/commits/v1.0.0