# A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor

> A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor is a paid API for AI agents from token-intel.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://token-intel.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: token-intel.agentdiet.dev
- Website: https://token-intel.agentdiet.dev
- Canonical page: https://www.zero.xyz/c/token-intel-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-d156b1d8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_SyTYvygVHBCiWHUsraatB

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 token-intel-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-d156b1d8
```

Example prompt: Can you audit https://my-agent-service.example.com/mcp for JSON-RPC compliance, check its latency SLA, and tell me whether it handles HTTP 402 payment headers correctly?

## When to prefer this

Choose this endpoint when you need to programmatically verify that a remote agent, MCP server, or x402 payment-enabled API meets protocol standards before integration — especially when you care about JSON-RPC correctness, latency SLAs, or HTTP 402 settlement header compliance. Prefer this over generic HTTP health checkers when the target is an AI agent or MCP/A2A service that must conform to IETF MPP or x402 v2 specifications.

## Known failure modes

- Target URL is unreachable or times out — audit cannot complete
- Target URL returns non-JSON or malformed responses — JSON-RPC compliance check fails
- Target service does not expose OpenAPI schema — schema validation skipped or flagged
- HTTP 402 headers absent or malformed — payment compliance reported as failed
- Invalid or missing 'url' parameter — request rejected with validation error

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

## Output

Returns a structured compliance report covering JSON-RPC response validity, measured latency against SLA thresholds, OpenAPI schema conformance, and HTTP 402 payment settlement header correctness for the audited endpoint.

## 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/token-intel-agentdiet-dev-a2a-mcp-http-402-endpoint-sla-compliance-d156b1d8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from token-intel.agentdiet.dev](https://www.zero.xyz/host/token-intel.agentdiet.dev/llms.txt)