Add MCP Observatory CI check#225
Open
KryptosAI wants to merge 1 commit into
Open
Conversation
Author
|
Small update: MCP Observatory v0.27.0 is now published with optional SARIF output and GitHub Code Scanning support. This PR can remain a read-only advisory compatibility/security check. If maintainers later want MCP findings in GitHub Code Scanning, the workflow can opt into Docs: https://github.com/KryptosAI/mcp-observatory/blob/main/docs/github-code-scanning-for-mcp.md |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds a lightweight MCP Observatory check for the Playwright MCP server.\n\nWhy it helps:\n\n- verifies MCP tools/resources still respond correctly\n- catches schema drift and common security footguns before release\n- posts a readable PR report for maintainers\n- gives users a compatibility signal when evaluating MCP servers\n\nI validated the target locally with:\n\n
bash\nnpx @kryptosai/mcp-observatory@latest test --target mcp-observatory.target.json --security --deep\n\n\nResult: passed, with 33 tools and 1 resource detected fromnpx -y @executeautomation/playwright-mcp-server@latest. The workflow installs Chromium first so the optional deep checks can initialize browser-backed tools.\n\nThe target config suppressesplaywright_evaluate:shell-injectionbecause arbitrary JavaScript evaluation is an intentional browser automation capability for this server, not an accidental shell execution surface. Everything else remains checked.\n\nIt runs in GitHub Actions and does not require an MCP Observatory account. If the check is too strict for this repo, the workflow can be adjusted while keeping the report visible.