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

• assay_get_ledger_policyFree

  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 target is unindexed. Idempotent; first 5 calls/IP are free. Use to audit historical drift or pin mcp-lock.json hashes; for live pre-execution gating use assay_preflight; for live re-indexing use assay_probe; for post-payment SLA receipts use assay_verify_delivery. Example: target='https://agentdiet-72343955726.us-central1.run.app/mcp'.

• assay_preflightFree

  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-only gate; first 5 calls/IP are free and quota-exceeded calls return a 402 top-up prompt. Use before tool execution or payment; to register or refresh public leaderboard telemetry use assay_probe; to read or pin stored policy hashes use assay_get_ledger_policy; after payment use assay_verify_delivery. Example: target='https://agentdiet-72343955726.us-central1.run.app/mcp'.

• assay_probeFree

  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. Writes to the public ledger; first 5 calls/IP are free and retries are idempotent on steady schemas. Use to onboard or re-index a server; for pre-call allow/deny gating use assay_preflight; for historical observations or hash pinning use assay_get_ledger_policy; for post-payment disputes use assay_verify_delivery. Example: target='https://agentdiet-72343955726.us-central1.run.app/mcp'.

• assay_verify_deliveryFree

  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 receipt). Non-destructive; first 5 calls/IP are free and failed target connections do not throw tool errors. Use only after paying a provider; before payment use assay_preflight; for public indexing use assay_probe; for policy history use assay_get_ledger_policy. Example: target='https://agentdiet-72343955726.us-central1.run.app/mcp'.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 724ms20/20
• Tool poisoning4 tool descriptions checked15/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenancelast push 9 days ago15/15
• Maintainer identityendpoint served from the registry-verified namespace domain8/10

Safety score

91/100

higher than 90% of 680 Maps and travel servers

Tools

4

the typical Maps and travel server has 6

Tools that change things

0%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote Maps and travel server answers 100%

Response time

80 ms

faster than 87% of 451 Maps and travel servers

Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory: common questions

Is Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory MCP server safe?

Yes, by our scan: it is graded A (91/100). Read the Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory safety report

How do I install Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory?

It runs remotely at assay.agentdiet.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory maintained?

The last commit was 16 days ago (2026-10-17). The latest release is v7.0.17.

Is Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory up?

100% of our last 25 checks got an answer. We check remote servers about four times a day.

What can I use instead of Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory?

Servers from other publishers that do the same job: Flightaware MCP server, Figuard MCP server and Variflight MCP server.

How does Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory compare with other Maps and travel MCP servers?

safety score 91/100 (higher than 90% of 680 Maps and travel servers); tools 4 (the typical Maps and travel server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.