A small GitHub Actions check for MCP configuration changes
I wanted a reviewer to see what an MCP config scan found in the same pull request where the team was already reviewing the change. I tried a report-only GitHub Actions check with MCPSense 0.5.1 and a disposable config.
I wanted a reviewer to see what an MCP config scan found in the same pull request where the team was already reviewing the change. I tried a report-only GitHub Actions check with MCPSense 0.5.1 and a disposable config.
Reproduce the two results
Save this in an empty folder as review-mcp.json:
{
"mcpServers": {
"sample": { "url": "http://example.invalid/mcp" }
}
}
With MCPSense 0.5.1 installed, run:
mcpsense scan ./review-mcp.json --mode config --offline --no-baseline
The offline scan reported one high finding, SEC-016, for plain HTTP. Change only http:// to https:// and run it again. The finding clears. This test covers the transport setting in the file. Server behavior, authorization, and tool responses still need separate review.
Try it in one pull request
The public Actions run shows both results. The setup guide links to the pinned workflow and explains how to point it at your config file.
The workflow puts the finding count in the job summary. During the trial, findings leave the check green and a failed scan fails the job. Run the same scan locally when you need the details.
If you already review MCP config changes in GitHub, Iβd like to hear what the report changes about one review. Thereβs an option in the guide to try it together for 20 minutes. Your repo and results can stay private.
Disclosure: I maintain MCPSense. I used AI assistance to draft this post and verified the demo against the published release.
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.