BRAINIAC Crypto Payments
Server Details
Paid Crypto Payments API via x402. Unpaid tool calls return 402.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 2 tools
Both tools compare caller-supplied payments against invoices, so an agent could easily confuse them. The descriptions do distinguish the outputs—one produces a weighted match score, the other produces reconciliation statuses and duplicate/mismatch detection—but the boundary is still fuzzy.
Both names use the same crypto-payments_ prefix and kebab-case, which is readable. However, the internal ordering is inconsistent: invoice-match-score is noun-verb-noun while stablecoin-payment-reconcile is noun-noun-verb, so there is no predictable verb_noun pattern.
Two tools is thin for a server framed as crypto payments, though it may be intentionally narrow. The count is borderline rather than clearly wrong.
The surface only covers scoring and reconciliation of caller-supplied records. There are no tools for creating or managing invoices, recording payments, listing records, or checking on-chain state, leaving significant lifecycle gaps for a crypto payments domain.
Available Tools
2 toolscrypto-payments_invoice-match-scoreScore invoice payment matchAInspect
Match caller-supplied payments to invoice amounts, due dates, and fee rates in basis points. Accuracy gives 60 points to the amount, 20 to paying on time, and 20 to the fee. The discrepancy is the invoice total minus the linked payments. No chain is queried. Price $0.04 USDC. POST /api/v1/crypto-payments/invoice-match-score. Unpaid calls return 402 and do not run.
Inputs: invoices (required), payments (required).
crypto-payments_stablecoin-payment-reconcileReconcile stablecoin paymentAInspect
Reconcile caller-supplied stablecoin payment records against invoices. Compares amounts, token, recipient, and chain ID, and reports underpayments, overpayments, duplicate transaction hashes, and payments that are not linked to an invoice. reconciliation_status is matched, underpaid, overpaid, duplicate, mismatched, or incomplete. Amounts are integers in smallest units. No chain is queried, and a transaction hash is not treated as confirmation that funds arrived. Price $0.05 USDC. POST /api/v1/crypto-payments/stablecoin-payment-reconcile. Unpaid calls return 402 and do not run.
Inputs: invoices (required), payments (required), rules.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Paid Crypto Operations API via x402. Unpaid tool calls return 402.
1Paid Crypto Governance API via x402. Unpaid tool calls return 402.
1Paid Crypto Security API via x402. Unpaid tool calls return 402.
1Paid Account Abstraction API via x402. Unpaid tool calls return 402.
1
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents and bots to buy per-call data and intelligence — token safety verdicts, prices, news, weather, web-to-text, and research dossiers — without signup or API keys, since each call is authenticated by an on-chain USDC payment on Base via the x402 protocol. Clients hit any paid endpoint, receive an HTTP 402 challenge, sign an EIP-3009 transfer authorization, and retry to get the data.1MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to pay per tool call in USDC via the x402 micropayment protocol, with no API keys or subscriptions required.-
- AlicenseAqualityCmaintenanceEnables agents to call paid utilities for DNS/SSL checks, site status, summarization, keyphrase extraction, decision advice, data cleanup, claim verification, and grounding via per-call USDC payments over x402, with free discovery tools and no signup or API key.10MIT
- FlicenseNot gradedqualityCmaintenancePay-per-call agent tools (web reader, page extract, email/domain/site/wallet/token checks, screenshot, PDF) via x402 USDC micropayments, with 3 free trial calls per wallet.-
Glama MCP Gateway
Add one secure layer between your agents and this server.