Chainguard ships four MCP servers so coding agents verify images, APKs, EOL status and policy live—server-side governance instead of prompt guardrails
On 2026-10-14 Chainguard announced four MCP servers for agent supply-chain checks, generally available to enterprise customers: cg-oci (image manifests/SBOMs/provenance), cg-apk (Wolfi package equivalents), cg-versions (upstream releases and EOL), and cg-api (org policy and attestations). Any MCP client (Claude Code, Cursor, and others) connects via OAuth; pagination and response caps are enforced server-side so agents stop hallucinating tags or recommending EOL packages. Complements the same-day Harness/Checks/Workspaces launch by wiring dependency choices to live product data.

Key Takeaways
- Four endpoints:
https://cgr.dev/mcp,apk.cgr.dev/mcp,versions.cgr.dev/mcp,console-api.enforce.dev/mcpover Streamable HTTP + OAuth 2.0 - Live data: image SBOM/provenance, Debian→Wolfi package mapping, upstream EOL history, org policy/advisories—not model memory
- Governance: server-side pagination (~25–50 default, 200 max) and response caps;
cg-apihides tools your token cannot use - Headless:
chainctl auth login --audience=<mcp-url>plus aheadersHelperBearer injector avoids Claude Code's ~1h OAuth re-login loop - Extras: docs MCP at
mcp.edu.chainguard.dev(no sign-in); Skills MCP atskills.cgr.dev/mcpfor on-demand hardening skills
