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

> Source: <https://dev.to/k08200/mcp-probe-v160-stricter-github-actions-checks-for-mcp-ci-gates-52k9>
> Published: 2026-05-26 04:35:59+00:00

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

.

Previous behavior:

`.github/workflows`

exists`mcp-probe`

That was useful, but too shallow. A workflow can mention `mcp-probe`

and still not run the actual CI gate correctly.

`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.

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

`tools/list`

discovery`tools/call`

dry-runsA readiness gate is only useful if the gate is actually installed correctly.

GitHub: [https://github.com/k08200/mcp-probe](https://github.com/k08200/mcp-probe)

npm: [https://www.npmjs.com/package/@k08200/mcp-probe](https://www.npmjs.com/package/@k08200/mcp-probe)

Release: [https://github.com/k08200/mcp-probe/releases/tag/v1.6.0](https://github.com/k08200/mcp-probe/releases/tag/v1.6.0)