# io.github.robertoyanguas-ops/assay

- Registry name: `io.github.robertoyanguas-ops/assay` · version 0.4.2
- Categories (automatic, keyword rules): Agent payments (x402), Finance & markets, Code & repositories, Developer tools, Travel & booking, Commerce & marketing
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.robertoyanguas-ops%2Fassay
- Server page: https://mcpstation.net/s/io.github.robertoyanguas-ops--assay.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

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

## Tools (as reported by the server, not verified)

- `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

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html