What problem does it solve?
Teams declaring MCP servers and tools in a harness configuration need a way to catch policy, permission, and dependency issues before deployment, without actually executing any of those tools.
Core Features & Use Cases
- Static MCP Surface Scan: Enumerates every declared MCP server and tool from
.mcp/servers.json and .harness/claims.json without dispatching or executing anything.
- Severity-Gated Exit Codes: Fails CI with exit code 1 when findings meet or exceed a configurable
--fail-on threshold (low, medium, or high).
- Graceful Degradation: Emits a structured
{ degraded: true } result and exits 0 when the harness binary is unavailable, so pipelines never hard-fail on tooling issues.
- Use Case: Add a CI step that runs the scan with
--fail-on high on every pull request, archiving the JSON findings as artifacts for security review.
Quick Start
Run a static security scan of the MCP servers declared in this repository and fail on any high-severity findings.