# Assay: settlement verification

- Registry name: `io.fomox/assay` · version 1.0.0
- Categories (automatic, keyword rules): Payments & accounting, Finance & markets, Crypto & blockchain
- Authentication at last check: No auth
- Declared risk: Not declared (tools carry no read/destructive hints)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.fomox%2Fassay
- Server page: https://mcpstation.net/s/io.fomox--assay.html

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

Verify crypto payments really settled and how much arrived. 20 chains. Read only, no API key.

## Connect

- streamable-http: `https://fomox.io/api/assay/mcp`

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

- `verify\_payment`: Check whether a crypto payment really settled and how much was ACTUALLY delivered, which is often not the amount the transaction claims. Use this before crediting anyone for an incoming payment. Returns \`delivered\` \(what truly moved\), \`claimed\` \(what the transaction says\), \`mismatch\` \(true when they
- `list\_chains`: List every chain this service can verify, with the confirmation depth each needs before a payment is treated as final, and how deeply it can be verified. Call this if you are unsure whether a chain is supported or what to pass as \`chain\`.
- `list\_failure\_modes`: List every known way a blockchain payment can appear successful while being worth less than it claims, or nothing at all. Each entry explains what the chain does, what it costs you when you get it wrong, and the one-line fix. Useful when writing or reviewing code that credits users for incoming cryp
- `evaluate\_spend\_policy`: Check a proposed payment against spending limits that live OUTSIDE your context, where no instruction in a prompt, a message or a web page can change them. Returns a signed allow or deny with reasons. Use this before executing any transfer on behalf of a user. It enforces velocity caps, per-action c
- `run\_sandbox\_case`: Practise on a payment designed to deceive you, with no money at risk. Returns a verification result shaped exactly like a real one for one of 19 adversarial cases. Decide whether you would credit it, then call check\_sandbox\_answer to find out whether you were right and what the mistake would have co
- `check\_sandbox\_answer`: Score your decision on a sandbox case. Tell it whether you would have credited the payment and for how much, and it replies with whether that was correct and, if not, exactly what the error would have cost you in real units. This is the fastest way to find out whether your payment handling is actual

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