# 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 any A2A 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/mpp-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-eb50c37a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_cZueCq_Ppwm6-6ucRF91d

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-eb50c37a
```

Example prompt: Can you audit https://myagent.example.com/mcp for JSON-RPC compliance, check its latency SLA, and tell me whether it has proper HTTP 402 x402 settlement headers configured?

## When to prefer this

Choose this endpoint when you need to programmatically verify that an A2A agent, MCP server, or x402-enabled service URL is correctly implementing JSON-RPC, HTTP 402 settlement, IETF MPP, or OpenAPI schemas — especially during CI/CD pipelines, pre-integration vetting, or ongoing agent fleet health monitoring. Prefer this over generic uptime checkers when protocol-level compliance (not just availability) is what matters.

## Known failure modes

- Target URL is unreachable or returns connection timeout
- Target URL does not respond with a recognizable JSON-RPC or HTTP 402 structure
- Invalid or malformed URL submitted in the query parameter
- Target URL blocks the auditor's probe requests (firewall/rate-limit)
- Incomplete compliance data returned if the target only partially implements a protocol

## 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/mpp-verifier)

## Output

Returns a structured compliance report detailing JSON-RPC adherence, measured latency vs SLA thresholds, OpenAPI schema validation results, and HTTP 402/x402 v2 payment settlement header inspection findings for the submitted 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-eb50c37a/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)