# A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor

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

Audits a remote A2A, 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://prompt-guard.agentdiet.dev/v1/mcp-security-scan?utm_source=zero.xyz
- Price: $0.01/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Provider: prompt-guard.agentdiet.dev
- Website: https://prompt-guard.agentdiet.dev
- Canonical page: https://www.zero.xyz/c/prompt-guard-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-8e230be5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IltJ8rcyZ46yoKjdW10lb

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 prompt-guard-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-8e230be5
```

Example prompt: Can you audit my MCP server at https://myagent.example.com/mcp for JSON-RPC compliance, latency SLA, and HTTP 402 payment header correctness?

## When to prefer this

Choose this endpoint when you need to programmatically verify that a specific A2A agent, MCP server, or x402-enabled service URL conforms to protocol standards — especially JSON-RPC structure, OpenAPI schema, HTTP 402 payment headers, and latency SLA. Prefer this over generic HTTP health checkers when the target is specifically an AI agent protocol endpoint and you need protocol-layer compliance details rather than simple uptime.

## Known failure modes

- Target URL is unreachable or times out — audit fails with connectivity error
- Target URL returns malformed or non-JSON response — JSON-RPC compliance check fails
- URL parameter missing or empty — request rejected with validation error
- Target service blocks automated probes — results may be incomplete
- Non-agent URL submitted (e.g. a plain website) — compliance checks return not-applicable or fail all checks

## 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://prompt-guard.agentdiet.dev/v1/mcp-security-scan)

## Output

Returns a structured compliance report covering: JSON-RPC protocol conformance, measured latency versus SLA thresholds, OpenAPI schema validity findings, and HTTP 402 / x402 payment header inspection results for the submitted 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/prompt-guard-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-8e230be5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from prompt-guard.agentdiet.dev](https://www.zero.xyz/host/prompt-guard.agentdiet.dev/llms.txt)