P0: CVE, package and domain checks
dev.workers.x402-bazaar-rank-worker.x402-bazaar-rank/cve-package-domain-security
CVE with EPSS and CISA KEV, package risk, software EOL, domain and IP reports, pay per call
Install surfaces
How P0: CVE, package and domain checks runs, per the official MCP registry entry.
- streamable-http
https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/cve-package-domain-security
Governed execution
How KLA gates calls to P0: CVE, package and domain checks once it is connected.
A published policy defines which P0: CVE, package and domain checks actions an agent may take and under what conditions. Each call passes through a policy gate at the tool-call boundary. Permitted actions execute, with the policy basis recorded. Flagged actions execute and are sampled for scheduled human review. High-stakes actions pause and route to a named reviewer on the Decision Desk. The call, the policy decision, and any approval are sealed as an evidence record.
KLA also governs the agents and model providers you already run. See integrations.