Validate MCP servers in CI

Validate MCP servers with contract testing and CI readiness

Proving in CI that your MCP server actually works on real tool calls, not just schemas.

• · MCP server target (npx package, local, or URL)
• · tool samples (dry-run input payloads)
• · contract assertions (shape, limits, error codes)

• · handshake receipt (initialize success)
• · tools/list discovery JSON
• · dry-run call results and timings
• · GitHub Actions summary
• · machine-readable JSON receipt

• · target MCP server (must be runnable)
• · sidecar config / tool samples

• · npx or local MCP server running successfully
• · config file with server and tool definitions (optional)
• · sidecar tool samples for meaningful calls

• · generated tool samples may not be safe (e.g., destructive operations)
• · no built-in auth scope validation
• · CI receipt requires manual review for false positives
• · schema discovery cannot validate internal logic

• · real-world failure mode focus
• · tested on multiple production servers
• · recipe-driven contract testing
• · GitHub Actions integration