mcp-probe v1.6.0: Stricter GitHub Actions checks for MCP CI gates

I shipped mcp-probe v1.6.0 with a small but useful improvement to mcp-probe doctor.

Previous behavior:

• check whether .github/workflows exists
• check whether any workflow mentions mcp-probe

That was useful, but too shallow. A workflow can mention mcp-probe and still not run the actual CI gate correctly.

What changed

mcp-probe doctor now warns when the matching GitHub Actions workflow is missing any of these pieces:

• actions/checkout@v6
• --config <config-file>
• --github-summary

Example:

npx @k08200/mcp-probe@latest doctor

If your workflow calls mcp-probe directly but does not use the configured fleet gate, doctor now tells you what is missing before you trust the CI result.

Why this matters

The larger goal of mcp-probe is to make MCP servers testable like normal infrastructure. That means checking more than process startup:

• MCP initialize handshake
• tools/list discovery
• real tools/call dry-runs
• sidecar sample inputs
• contract assertions for row limits, stable error codes, and leak checks
• and now, whether the CI workflow itself is wired correctly

A readiness gate is only useful if the gate is actually installed 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.6.0