Paid Crypto Payments API via x402. Unpaid tool calls return 402.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
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. An unpaid call returns the x402 payment terms and does not run.
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http crypto-payments https://www.brainiac.software/mcp/crypto-payments
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. An unpaid call returns the x402 payment terms and does not run.
| Argument | Type | Description |
|---|---|---|
| invoices* | array | |
| payments* | array |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"invoices",
"payments"
],
"properties": {
"invoices": {
"type": "array",
"items": {
"type": "object",
"required": [
"id",
"amount"
],
"properties": {
"id": {
"type": "string",
"maxLength": 80,
"minLength": 1
},
"amount": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0
},
"due_on": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"fee_bps": {
"type": "integer",
"maximum": 10000,
"minimum": 0
}
}
},
"maxItems": 200,
"minItems": 1
},
"payments": {
"type": "array",
"items": {
"type": "object",
"required": [
"invoice_id",
"amount"
],
"properties": {
"fee": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0
},
"amount": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0
},
"paid_on": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"invoice_id": {
"type": "string",
"maxLength": 80,
"minLength": 1
}
}
},
"maxItems": 400
}
}
}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. An unpaid call returns the x402 payment terms and does not run.
| Argument | Type | Description |
|---|---|---|
| rules | object | |
| invoices* | array | |
| payments* | array |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"invoices",
"payments"
],
"properties": {
"rules": {
"type": "object",
"properties": {
"tolerance": {
"type": "string"
},
"allowPartial": {
"type": "boolean"
},
"associateUnlabeledPayments": {
"enum": [
"none",
"single_invoice"
],
"type": "string"
}
},
"additionalProperties": false
},
"invoices": {
"type": "array",
"items": {
"type": "object",
"required": [
"id",
"amount",
"decimals",
"token",
"chainId",
"recipient"
],
"properties": {
"id": {
"type": "string",
"maxLength": 80,
"minLength": 1
},
"token": {
"type": "string",
"pattern": "^0x[0-9a-fA-F]{40}$"
},
"amount": {
"type": "string"
},
"chainId": {
"type": "integer",
"maximum": 2147483647,
"exclusiveMinimum": 0
},
"decimals": {
"type": "integer",
"maximum": 36,
"minimum": 0
},
"recipient": {
"type": "string",
"pattern": "^0x[0-9a-fA-F]{40}$"
},
"tolerance": {
"type": "string"
}
},
"additionalProperties": false
},
"maxItems": 40,
"minItems": 1
},
"payments": {
"type": "array",
"items": {
"type": "object",
"required": [
"amount",
"decimals",
"token",
"chainId",
"recipient"
],
"properties": {
"id": {
"type": "string",
"maxLength": 80,
"minLength": 1
},
"token": {
"type": "string",
"pattern": "^0x[0-9a-fA-F]{40}$"
},
"amount": {
"type": "string"
},
"chainId": {
"type": "integer",
"maximum": 2147483647,
"exclusiveMinimum": 0
},
"decimals": {
"type": "integer",
"maximum": 36,
"minimum": 0
},
"invoiceId": {
"type": "string",
"maxLength": 80,
"minLength": 1
},
"recipient": {
"type": "string",
"pattern": "^0x[0-9a-fA-F]{40}$"
},
"timestamp": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}(?:\\.\\d{1,3})?Z$"
},
"transactionHash": {
"type": "string",
"pattern": "^0x[0-9a-fA-F]{64}$"
}
},
"additionalProperties": false
},
"maxItems": 100
}
},
"additionalProperties": false
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 19, 2026.
Takes a password, API key or token as an argument, so the secret passes through the model's context and chat logs.
Fix: Read credentials from the server's own configuration (environment, OAuth) instead of a tool argument.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.