# A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor

> A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor is a paid API for AI agents from onchain-risk.agentdiet.dev, paid per call via MPP, $0.01/call, status unknown (last checked 2026-11-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: POST https://onchain-risk.agentdiet.dev/v1/mcp-security-scan?utm_source=zero.xyz
- Price: $0.01/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-11-21
- Activations on Zero: 0
- Provider: onchain-risk.agentdiet.dev
- Website: https://onchain-risk.agentdiet.dev
- Canonical page: https://www.zero.xyz/c/onchain-risk-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-8f0ebbdc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wJxLV_dcvFqfy3JYSCKpr

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 onchain-risk-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-8f0ebbdc -d '<json body>'
```

Example prompt: Can you audit my MCP endpoint at https://myagent.example.com/mcp and tell me if it passes JSON-RPC compliance, meets latency SLA, has a valid OpenAPI schema, and has the right HTTP 402 settlement headers configured?

## When to prefer this

Use this endpoint when you need to programmatically verify that an A2A agent, MCP server, or x402-enabled payment endpoint conforms to protocol standards before deployment or as part of ongoing monitoring. Prefer this over manual testing or generic HTTP probers when you need structured compliance reports covering JSON-RPC, OpenAPI schema, SLA latency, and HTTP 402 payment header compliance in a single call.

## Known failure modes

- Target URL is unreachable or returns a network error
- Target endpoint times out during latency measurement
- Invalid or malformed URL submitted in the request body
- Target service returns unexpected non-standard responses that prevent schema parsing
- Missing or malformed HTTP 402 headers cause 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://onchain-risk.agentdiet.dev/v1/mcp-security-scan)

## Output

Returns a structured audit report covering: JSON-RPC protocol compliance status, measured latency vs SLA thresholds, OpenAPI schema validation findings, and HTTP 402 / x402 settlement header inspection results 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/onchain-risk-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-8f0ebbdc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from onchain-risk.agentdiet.dev](https://www.zero.xyz/host/onchain-risk.agentdiet.dev/llms.txt)
