DEV Community

Faizan Khan
Faizan Khan

Posted on Edited on

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.

Reproduce the two results

Save this in an empty folder as review-mcp.json:

{
  "mcpServers": {
    "sample": { "url": "http://example.invalid/mcp" }
  }
}
Enter fullscreen mode Exit fullscreen mode

With MCPSense 0.5.1 installed, run:

mcpsense scan ./review-mcp.json --mode config --offline --no-baseline
Enter fullscreen mode Exit fullscreen mode

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 version-pinned workflow shows how the scan and job summary fit together. If your config path differs, update the trigger, file check, and scan target together.

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.

Disclosure: I maintain MCPSense. I used AI assistance to draft this post and verified the demo against the published release.

Top comments (0)