# A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor

> A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor is a paid API for AI agents from mcp-security.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, OpenAPI schema validity, and HTTP 402 payment settlement headers

## Facts

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

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 mcp-security-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-d6a0c406
```

Example prompt: Can you audit https://my-agent.example.com/mcp to check whether it's JSON-RPC compliant, passes latency SLA, has a valid OpenAPI schema, and returns the correct HTTP 402 x402 v2 settlement headers?

## When to prefer this

Use this endpoint when you need to programmatically verify that a specific remote agent, MCP server, or x402 paywall URL conforms to JSON-RPC, OpenAPI, HTTP 402 x402 v2, and IETF MPP protocol standards — especially before integrating a third-party agent endpoint or before launching your own. Prefer this over generic uptime monitors when protocol-level compliance (not just liveness) is what matters.

## Known failure modes

- Target URL unreachable or returns network error — audit fails with connectivity error
- Target URL returns unexpected content type (e.g. HTML instead of JSON) — JSON-RPC compliance check fails
- Malformed or missing URL parameter — request rejected with validation error
- Target service too slow to respond — latency SLA flagged as failed
- x402 headers absent or malformed — HTTP 402 compliance reported as non-conformant

## 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://mcp-security.agentdiet.dev/v1/x402-mpp-paywall-verifier)

## Output

Returns a structured compliance report covering JSON-RPC protocol adherence, measured latency against SLA thresholds, OpenAPI schema validation findings, and HTTP 402 x402 v2 / IETF MPP settlement header correctness for the target 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/mcp-security-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-d6a0c406/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from mcp-security.agentdiet.dev](https://www.zero.xyz/host/mcp-security.agentdiet.dev/llms.txt)