All servers · Agent payments (x402) · Code & repositories · Travel & booking

io.github.robertoyanguas-ops/assay

io.github.robertoyanguas-ops/assay · v0.4.2

Tools changed (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%

A2A & MCP Pre-Flight Security: SHA-256 tool schema rug-pull detection and liveness grades.

streamable-http · https://assay-207908449630.us-central1.run.app/mcp

claude mcp add --transport http assay https://assay-207908449630.us-central1.run.app/mcp

{
  "mcpServers": {
    "assay": {
      "url": "https://assay-207908449630.us-central1.run.app/mcp"
    }
  }
}

assay_preflight
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
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 timesta
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 paymen
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 omit

2026-10-19: assay_preflight, assay_probe, assay_verify_delivery, assay_get_ledger_policy
2026-10-18: assay_preflight, assay_probe, assay_verify_delivery, assay_get_ledger_policy
2026-10-17: assay_preflight, assay_probe, assay_verify_delivery

JSON · Text for agents · Registry updated 2026-10-16