# 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 A2A agent, MCP server, or x402-enabled 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-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-0833aa02
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xyjGLfZUm8LPIlsNRySY-

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-0833aa02
```

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

## When to prefer this

Use this endpoint when you need to programmatically verify that an A2A agent, MCP server, or x402-enabled API endpoint correctly implements one or more of: JSON-RPC protocol, latency SLA thresholds, OpenAPI schema, or HTTP 402 x402 payment settlement headers. It is particularly valuable for pre-deployment checks, third-party agent integration due diligence, and marketplace listing compliance. Prefer it over generic HTTP probing tools when the target is specifically an agent or MCP endpoint with payment or protocol compliance requirements.

## Known failure modes

- Target URL is unreachable or returns a connection timeout — audit returns network error
- Target URL does not implement JSON-RPC — compliance check fails with protocol mismatch
- Missing or malformed x402 headers — HTTP 402 check fails with header validation error
- URL parameter is missing or empty — request rejected with validation error
- Target service returns unexpected HTTP status codes — partial audit results returned

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

## Output

Returns a structured compliance report covering JSON-RPC response validity, measured latency against SLA thresholds, OpenAPI schema presence and correctness, and HTTP 402 x402 payment header fields — indicating which checks passed, failed, or were not applicable 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/mcp-security-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-0833aa02/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)