I shipped mcp-probe v1.6.0 with a small but useful improvement to mcp-probe doctor. Previous...
mcp-probe v1.6.0 upgrades `doctor` to flag CI workflows missing `actions/checkout`, `--config`, or `--github-summary`, beyond just detecting any mention of the tool. A misconfigured gate silently skips MCP handshake, tool-discovery, and dry-run checks—making the CI result meaningless.
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.
mcp-probe started as a small CLI for checking whether an MCP server starts and exposes tools. That...
MCP servers are starting to look like infrastructure. That means the old readiness question is no...
Your CI workflow is the softest target in your repo. It runs automatically, it has a GITHUB_TOKEN...
I just published my first GitHub Marketplace Action: Aster Guard...
I removed four || true statements from a GitHub Actions workflow on July 9th and watched CI go red in...
The 2026 pricing changes got me curious how the projects I actually use run their CI. So I scanned 35...
