# A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor

> A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor is a paid API for AI agents from cve-intel.agentdiet.dev, paid per call via MPP, $0.01/call, status unknown (last checked 2026-10-21).

Audits a remote agent, MCP, or x402 service URL for JSON-RPC compliance, latency SLA adherence, OpenAPI schema validity, and HTTP 402 payment settlement headers

## Facts

- Endpoint: GET https://cve-intel.agentdiet.dev/v1/mpp-verifier?utm_source=zero.xyz
- Price: $0.01/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Provider: cve-intel.agentdiet.dev
- Website: https://cve-intel.agentdiet.dev
- Canonical page: https://www.zero.xyz/c/cve-intel-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-2ee64833
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_59FaUcx9PN0Ur9awMPqFY

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability cve-intel-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-2ee64833
```

Example prompt: Can you audit https://my-agent-service.example.com/mcp and tell me whether it passes JSON-RPC compliance, meets latency SLA, has a valid OpenAPI schema, and has its HTTP 402 settlement headers set up correctly?

## When to prefer this

Choose this endpoint when you need to programmatically verify that a remote agent, MCP server, or x402-enabled API meets protocol compliance standards — specifically JSON-RPC correctness, latency SLAs, OpenAPI schema validity, and HTTP 402 settlement header configuration. Prefer this over manual inspection or generic HTTP testing tools when you need structured compliance output across multiple protocol dimensions in a single call.

## Known failure modes

- Target URL is unreachable or returns a network timeout
- Target URL does not expose a valid JSON-RPC or MCP interface, resulting in a failed compliance check
- Malformed or missing URL parameter causes a 400 validation error
- Target service blocks probe requests, returning 403 or firewall rejection
- Ambiguous or incomplete OpenAPI schema at target causes partial audit results

## How this service works

Audits any remote agent or MCP URL for JSON-RPC compliance, latency SLA, OpenAPI schema, and HTTP 402 settlement headers. (Live x402 v2, IETF MPP & MCP endpoint at https://cve-intel.agentdiet.dev/v1/mpp-verifier)

## Output

Returns a compliance report covering JSON-RPC protocol conformance, measured latency vs SLA thresholds, OpenAPI schema validity, and the presence/correctness of HTTP 402 payment settlement headers for the audited URL

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "url"
 ],
 "properties": {
  "url": {
   "type": "string",
   "minLength": 1,
   "description": "Target A2A, MCP, or x402 service URL to audit for protocol compliance"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/cve-intel-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-2ee64833/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from cve-intel.agentdiet.dev](https://www.zero.xyz/host/cve-intel.agentdiet.dev/llms.txt)