All servers · Agent payments (x402)
Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory
dev.agentdiet/assay · v7.0.17
New (7 days)
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Can write (some tools are not declared read-only) |
| Capabilities declared | prompts, resources, tools |
| Tool definitions | 4 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
Live behavioral security verifier, schema auditor, and trust oracle for A2A, MCP & x402 agents.
Connect
streamable-http · https://assay.agentdiet.dev/mcp
claude mcp add --transport http assay https://assay.agentdiet.dev/mcp{
"mcpServers": {
"assay": {
"url": "https://assay.agentdiet.dev/mcp"
}
}
}Tools as reported by the server
assay_preflightGate 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 blockassay_probeRegister 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 timestaassay_verify_deliveryAudit 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 paymenassay_get_ledger_policyRetrieve 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 omit
Repository · Website · JSON · Text for agents · Registry updated 2026-10-21