mcp-probe v1.6.0: Stricter GitHub Actions checks for MCP CI gates
The release of mcp-probe v1.6.0 introduces stricter checks for GitHub Actions workflows related to MCP CI gates. The update enhances the mcp-probe doctor tool to ensure that necessary components are included in the workflows. This improvement aims to ensure that MCP servers are testable and that CI results are reliable.
- ▪The mcp-probe v1.6.0 update includes stricter checks for GitHub Actions workflows.
- ▪The mcp-probe doctor tool now warns users if essential components are missing from their workflows.
- ▪The goal of these changes is to make MCP servers testable like normal infrastructure.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3936365) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } yongrean Posted on May 26 mcp-probe v1.6.0: Stricter GitHub Actions checks for MCP CI gates #mcp #ai #githubactions #devops 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.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
