Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory
dev.agentdiet/assayagentdiet.devstreamable-httpv7.0.17Scanned
Live behavioral security verifier, schema auditor, and trust oracle for A2A, MCP & x402 agents.
4 tools: 4 change things.
- Reads private data · 0
- Reads text others write · 4
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory can do
The Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory is published by agentdiet.dev, a domain the MCP Registry verified. It has 4 tools. It can create or change data (4 tools: assay_preflight, assay_probe, assay_verify_delivery and assay_get_ledger_policy), but cannot delete data. None of its tools only reads.
4 tools bring in text other people can write (assay_preflight, assay_probe, assay_verify_delivery and 1 more).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 17, 2026, version 7.0.17.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 4Claude Code: ask
assay_get_ledger_policyRetrieve historical conformance observations and manage pinned SHA-256 tools/list policy hashes in the Assay ledger for a target endpoint.Reads text others write1 finding
Why it is in this group
- The name "assay_get_ledger_policy" says "get": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "assay_get_ledger_policy" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "assay_get_ledger_policy" says "get": a word for reading.
Description, as the server wrote it 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'.
Annotations the server declares
- title: Query Historical Ledger & Pin Expected Schema Hashes
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
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 poisonin…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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'.
Annotations the server declares
- title: Pre-Flight MCP & A2A Security Gate
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
assay_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 poli…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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'.
Annotations the server declares
- title: Register & Refresh Endpoint Conformance Telemetry
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
assay_verify_deliveryAudit a paid x402 or A2A provider after payment to confirm delivery or prove an SLA breach with an HMAC-SHA256 signed receipt.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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'.
Annotations the server declares
- title: Verify Post-Payment x402 Delivery & Mint SLA Receipt
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:22 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://assay.agentdiet.dev/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://assay.agentdiet.dev
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://assay.agentdiet.dev/mcp: tools/list returned 4 tools to an anonymous client, including assay_preflight (write), assay_probe (write), assay_verify_delivery (write), assay_get_ledger_policy (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "assay_get_ledger_policy" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "assay_get_ledger_policy" says "get": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 7.0.17. Values in angle brackets are yours to fill in.
claude mcp add --transport http assay https://assay.agentdiet.dev/mcpclaude mcp add --transport http assay https://assay.agentdiet.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__assay__assay_preflight",
"mcp__assay__assay_probe",
"mcp__assay__assay_verify_delivery",
"mcp__assay__assay_get_ledger_policy"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as assay. Review it before you use it.
Capability tags behind 4 rules
- mcp__assay__assay_preflight untrusted-input
- mcp__assay__assay_probe untrusted-input
- mcp__assay__assay_verify_delivery untrusted-input
- mcp__assay__assay_get_ledger_policy untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/dev.agentdiet/assay/verify?hash=54c73fce927cb97637d187f95a5e1e98f3218727f8a57c9e8b13de84e30c8ef9" | jq -e '.changed == false'Pinned hash 54c73fce927c, from Nov 17, 2026, 06:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.agentdiet/assay/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.agentdiet/assay)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:11 UTC.
Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory safe?
- No scan can promise that. What its definitions show: 4 tools, 4 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory have?
- 4 tools: 4 write. assay_preflight, assay_probe, assay_verify_delivery and assay_get_ledger_policy.
Does the Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Assay A2A, MCP & x402 Pre-Flight Verifier & Observatory changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.