mcp-probe v1.5.0: Doctor checks for MCP CI readiness

#mcp #ai #devops #node

MCP servers are starting to look like infrastructure. That means the tooling around them needs boring preflight checks, not just optimistic smoke tests.

I just shipped mcp-probe v1.5.0 with a new command:

npx @k08200/mcp-probe@latest doctor

mcp-probe doctor checks whether the current repository is ready to run MCP readiness checks in CI before you even probe an external server.

What it checks

Node.js runtime satisfies mcp-probe requirements
mcp-probe.config.json exists and parses
configured sidecar files exist and have valid tools.*.input objects
GitHub Actions workflows are present and mention mcp-probe

Example:

mcp-probe doctor --config-file examples/self-check.config.json

Output:

mcp-probe doctor
────────────────────────────────────────────────────
  ✓  Node.js version
     Node 24.13.0 satisfies >=20.19.0
  ✓  Config file
     examples/self-check.config.json contains 1 server
  ✓  Sidecar examples/self-check.tools.json
     Found 4 tool entries
  ✓  GitHub Actions workflow
     Found 1 workflow file mentioning mcp-probe
────────────────────────────────────────────────────
  PASS

For automation:

mcp-probe doctor --output json

Why this matters

The earlier releases focused on the MCP server itself:

initialize handshake
tools/list discovery
real tools/call dry-runs
sidecar sample inputs
contract assertions for row limits, metadata, stable error codes, and leak checks

But teams still need to know whether their own probe setup is sane. A broken config file, missing sidecar, or workflow that never invokes the probe should fail early and loudly.

This release is a small step, but an important one: before testing the MCP contract an agent depends on, test that your CI gate is actually wired correctly.

GitHub: https://github.com/k08200/mcp-probe
npm: https://www.npmjs.com/package/@k08200/mcp-probe
Release: https://github.com/k08200/mcp-probe/releases/tag/v1.5.0