Skip to content

mcp-doctor v0.2.0

Choose a tag to compare

@github-actions github-actions released this 11 Aug 19:53
· 87 commits to main since this release
Immutable release. Only release title and notes can be modified.
v0.2.0
b0805a8

mcp-doctor v0.2.0

mcp-doctor v0.2.0 expands the passive local preflight into a bounded,
explicitly authorized diagnostic workflow for local STDIO and remote
Streamable HTTP MCP 2026-07-28 servers.

It adds:

  • reviewed check scenarios for 1–100 ordered calls to one exact tool, gated
    by matching --allow-tool authority and separate side-effect consent;
  • direct, zero-redirect and zero-retry Streamable HTTP with pinned bounded
    resolution, verified TLS, exact private/cleartext/credential gates, and no
    automatic OAuth flow;
  • deterministic break generation for bounded, schema-valid cases against one
    redundantly selected and authorized tool;
  • authoritative, schema-backed mcp-doctor.report/v1 JSON across passive,
    reviewed active, generated, STDIO, and HTTP journeys; and
  • a deterministic, bounded JUnit-compatible projection that maps each
    diagnostic check to one test case without rerunning the target.

Human, JSON, and JUnit output derive from the same redacted result. Stable JSON
preserves the full contract; JUnit preserves safe findings, causal skips,
outcomes, and exit metadata in the common subset accepted by the reviewed
Jenkins and GitLab consumers. The process exit remains the portable CI gate.

Install the exact version with Cargo:

cargo install mcp-doctor --version '=0.2.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. This release does not add SARIF.
It does not become a general security scanner. It also does not implement older MCP
revisions, call a tool without exact run authority, contact a real endpoint in
the default suite, or ship project-issued macOS or Windows binaries.

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