Skip to content

mcp-doctor v0.3.0

Choose a tag to compare

@github-actions github-actions released this 14 Aug 00:02
· 60 commits to main since this release
Immutable release. Only release title and notes can be modified.
v0.3.0
d9b96bb

mcp-doctor v0.3.0

mcp-doctor v0.3.0 turns several common authoring and CI workflows into
bounded, explicit product paths while keeping the existing passive-first and
exact-authorization contracts.

It adds:

  • explicit passive inspect support for MCP 2025-11-25 and 2025-06-18
    over STDIO and Streamable HTTP, with no auto-detection, retry, fallback, or
    active legacy tool calls;
  • exact-opt-in current-revision contract snapshots and deterministic offline
    diffs, with a deliberate sensitive-artifact acknowledgement and no target
    activity during comparison;
  • simultaneous JSON and JUnit report files from the same redacted diagnostic
    run, without restarting a server or replaying an authorized tool call;
  • conservative offline aggregation of one through 32 stable JSON reports,
    preserving failures, incomplete outcomes, primary diagnoses, independent
    safety findings, and causal skips without contacting a target; and
  • correct protocol-layer diagnosis when a current-revision Streamable HTTP
    server returns the exact structured unsupported-version response.

The unsupported-version correction accepts only the bounded specification
shape. It never renders the server's error prose or offered revision values,
and it does not retry, initialize, downgrade, or fall back.

Install the exact version with Cargo:

cargo install mcp-doctor --version '=0.3.0' --locked

Or build the immutable source through Homebrew on macOS or GNU/Linux:

brew install --build-from-source EnjoyableWork/tap/mcp-doctor

Native archives remain limited to GNU/Linux ARM64 and x64. Source installs are
verified on represented macOS, GNU/Linux, and Windows hosts. Active check and
break remain limited to MCP 2026-07-28. This release does not add SARIF,
become a general security scanner, claim broad real-server legacy
compatibility, or ship project-issued macOS or Windows binaries.

See the release integrity guide for the artifact, provenance,
and installed-channel verification contract.