Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory

dev.agentdiet/assay

Live behavioral security verifier, schema auditor, and trust oracle for A2A, MCP & x402 agents.

Yes, your AI can use this right now.Answered a live MCP handshake in 279 ms with no sign-in needed and exposes 4 tools.
Is this your server? Claim the listing. Verified adds a vendor-confirmed mark on this page and matching app pages.
Claim with Verified — $49/moWant it in front of people comparing Security tools? Feature it — $149/mo

Connect it

Settings → Connectors → Add custom connector
URL: https://assay.agentdiet.dev/mcp

4 tools, pulled live

Pulled straight from the server with tools/list on 2026-10-27.
assay_preflightread-only

Gate a remote MCP, A2A, or x402 endpoint before calling or paying it by probing live JSON-RPC reachability, hashing tools/list (SHA-256), and scanning for prompt-injection poisoning. When expected_tools_hash is provided, any mismatch against the live tools/list digest forces verdict='deny' to block silent schema rug-pulls; when omitted, verdict reflects liveness and injection safety alone. Read-on

assay_probe

Register a new remote MCP, A2A, or x402 endpoint or refresh its public Assay Observatory dossier by running a live HTTP, agent-card, and JSON-RPC tools/list inspection without policy gating. Target must be a public HTTPS origin (private IPs are rejected with a 400 error); each call appends a timestamped observation and increments rug_pulls if tools_hash drifted since the prior stored observation.

assay_verify_delivery

Audit a paid x402 or A2A provider after payment to confirm delivery or prove an SLA breach with an HMAC-SHA256 signed receipt. Passing status_code >= 500 forces verdict='sla_breach_confirmed' even if the live re-probe succeeds, while passing tx_hash cryptographically binds your Base or Solana payment signature into the receipt (omitting tx_hash still verifies liveness and issues a probe-bound rece

assay_get_ledger_policy

Retrieve historical conformance observations and manage pinned SHA-256 tools/list policy hashes in the Assay ledger for a target endpoint. When expected_tools_hash is provided, it pins that 64-hex digest as the target's baseline policy and compares it against the latest stored observation; when omitted, it returns the stored dossier and last 20 drift observations without network probing unless the

Alternatives in Security

Compare →
Try “Notion”, “Stripe”, “create invoice”, “browser”