BRAINIAC Crypto Payments
Paid Crypto Payments API via x402. Unpaid tool calls return 402.
Description as published in the official MCP registry.
Maintain this server? Get the badge
What we measured
| Endpoint | https://www.brainiac.software/mcp/crypto-payments | registry |
|---|---|---|
| Website | www.brainiac.software | registry |
| Handshake | Answers the MCP handshake and lists its tools (278 ms) | our check, 2026-11-21 |
| Protocol version | 2025-11-25 | our check, 2026-11-21 |
| Tools (2) | crypto-payments_stablecoin-payment-reconcile, crypto-payments_invoice-match-score | tools/list, 2026-11-21 |
| Registry version | 1.0.1 · active · updated 2026-11-20 | registry |
Signed reports
No signed reports yet. A report carries a signed decision record from the reporter's gate, so it shows that the gate allowed a call, not just an opinion; it does not prove which server answered. How to file one.
Connect
claude mcp add --transport http crypto-payments https://www.brainiac.software/mcp/crypto-paymentsCommands are built from the registry entry. Check the publisher's documentation before giving any server access to your data.
Related servers
- BRAINIAC Bank Account Identifiers & Payment Files Paid Bank Account Identifiers & Payment Files API via x402. Unpaid tool calls return 402.
- BRAINIAC Card Payments, SCA & APP Scam Rules Paid Card Payments, SCA & APP Scam Rules API via x402. Unpaid tool calls return 402.
- BRAINIAC Crypto Governance Paid Crypto Governance API via x402. Unpaid tool calls return 402.
- BRAINIAC Crypto Operations Paid Crypto Operations API via x402. Unpaid tool calls return 402.
- BRAINIAC Crypto Security Paid Crypto Security API via x402. Unpaid tool calls return 402.
- BRAINIAC Crypto Tax Computation Paid Crypto Tax Computation API via x402. Unpaid tool calls return 402.
Is this your server?
Show the result of our latest check where your users look first. The badge is a live image: it changes when our check does, and it links back to this page.
[](https://openforallofus.com/tools/software.brainiac/crypto-payments)<a href="https://openforallofus.com/tools/software.brainiac/crypto-payments"><img src="https://openforallofus.com/badge/software.brainiac/crypto-payments.svg" alt="Agora: MCP handshake check" height="20"></a>The badge reports one thing: the result of our last handshake check. A server with no remote endpoint shows as "runs locally". How we check.
Agents can read this page as data: MCP endpoint https://openforallofus.com/api/mcp, tool get_tool with name software.brainiac/crypto-payments.