BRAINIAC Card Payments, SCA & APP Scam Rules
Pay-per-call MCP server for card payment rules, SCA and APP scam checks via x402
Answered our latest tool-list check 23 hours ago with 6 tools. It will be marked verified after 3 successful checks in 7 days.
BRAINIAC Card Payments, SCA & APP Scam Rules is a paid MCP server for finance and payments. It runs as a hosted remote server, so there is nothing to install locally.
- Pricing
- Paid
- Platforms
- API
- Runs
- Remotely
- Version
- 1.0.1
- Listing updated
Similar MCP servers
Install
Run in a terminal
claude mcp add --transport http card-payments https://www.brainiac.software/mcp/card-paymentsAdd to Settings → Connectors → Add custom connector
https://www.brainiac.software/mcp/card-paymentsAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"card-payments": {
"url": "https://www.brainiac.software/mcp/card-payments"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"card-payments": {
"type": "http",
"url": "https://www.brainiac.software/mcp/card-payments"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"card-payments": {
"serverUrl": "https://www.brainiac.software/mcp/card-payments"
}
}
}Add to Grok Bot desktop app → Connect apps → Add a custom connector
https://www.brainiac.software/mcp/card-paymentsEnter a Name (for example "BRAINIAC Card Payments, SCA & APP Scam Rules"), choose Type: Remote HTTPS, paste this as the Server URL and choose Add plugin.
Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"card-payments": {
"type": "http",
"url": "https://www.brainiac.software/mcp/card-payments"
}
}
}Using several servers? Build one config file with the MCP config generator.
About BRAINIAC Card Payments, SCA & APP Scam Rules
The BRAINIAC card-payments server gives AI agents access to rules covering card payment processing, strong customer authentication (SCA) and authorised push payment (APP) scam checks. It is listed in the official MCP registry under the name software.brainiac/card-payments and is reached over streamable HTTP at the vendor's own endpoint.
There is no account or API key step described on the vendor site. Each tool call is priced in USDC on Base through the x402 protocol, and an unpaid call returns an HTTP 402 response that tells the client to pay before retrying. The vendor describes its catalogue as fixed-price per call rather than a subscription.
The server suits developers building agents or payment workflows that need compliance answers to be looked up programmatically instead of hard-coded, and who are comfortable paying per request in stablecoin.
Tools this server provides (6)
Read directly from the server.
All 6 tools say they're read-only.
From the server's own tool annotations; not verified by us.
- card-payments_pan-checkSays read-only
- Check card number length and Luhn check digit before you authorise or store a card number. Never echoes the full PAN; returns masked form and last4 only. Returns length, luhnValid, last4, and masked. Carrying a payment-signature is not yet a charge. Settlement happens only on HTTP 2xx. Invalid JSON or schema returns HTTP 400 and is not charged. HTTP 200 with status complete, partial, or failed is
- card-payments_pan-maskSays read-only
- PCI DSS display masking for a single PAN, or find and redact Luhn-valid PANs in free text before you display, log, or store a card number. Call with optional pan, text, binLength. Returns masked. Carrying a payment-signature is not yet a charge. Settlement happens only on HTTP 2xx. Invalid JSON or schema returns HTTP 400 and is not charged. HTTP 200 with status complete, partial, or failed is char
- card-payments_interchange-cap-checkSays read-only
- Compute regulated maximum interchange under EU IFR consumer caps or US Reg II debit caps and flag fees above the cap before you charge or review a card interchange fee. Call with regime, cardType, amount, and currency; optional actualFee, regulatedIssuer, fraudAdjustmentEligible, domesticCapOverride. Returns capMinor, capExact, capFormula, exceedsCap, and excessMinor. HTTP 200 with status complete
- card-payments_sca-exemption-evaluateSays read-only
- Decide which PSD2 RTS SCA exemptions may apply to a remote or contactless payment from caller-supplied facts before you authorise or refund a card payment. Call with channel, instrument, and amountEur; optional sinceLastSca, trustedBeneficiary, trustedBeneficiaryListChanging, recurringSameAmountSamePayee, firstInSeries, sameOwnerSameAspsp and others. HTTP 200 with status complete, partial, or fail
- card-payments_app-scam-reimbursementSays read-only
- Calculate the UK mandatory APP scam reimbursement amount and 50:50 receiving-PSP contributions under PSR rules before you authorise or refund a card payment. Call with scheme, payments, and claimDate; optional excessApplied, vulnerable, exceptionsAsserted. Returns eligible, claimValue, cappedValue, excess, requiredReimbursement, receivingPspShares. HTTP 200 with status complete, partial, or failed
- card-payments_psd2-certificate-rolesSays read-only
- Parse a TPP QWAC/QSealC certificate for PSD2 roles, NCA and authorisation number before you authorise or refund a card payment. Does not verify the chain. Call with certificatePem. Returns subject, issuer, notBefore, notAfter, organizationIdentifier, authorisation, psd2, and issues (authorisation includes country, nca, number). HTTP 200 with status complete, partial, or failed is charged at the fu
What it does
- Pay-per-call access
- Each tool call is charged a fixed USDC amount on Base using the x402 payment protocol.
- No account setup
- The vendor says no account is needed; unpaid requests receive a 402 response with payment instructions.
- Card payment rules
- Covers rules relevant to card payments as named in the registry entry.
- SCA and APP scam rules
- Provides strong customer authentication and APP scam rule lookups.
- Streamable HTTP transport
- Connects to MCP clients over a streamable HTTP remote endpoint.
Good for
- Checking whether a payment flow needs strong customer authentication before an agent completes it
- Screening payment journeys against authorised push payment scam rules
- Adding compliance lookups to an agent workflow without managing API keys
- Pricing a per-request compliance check inside an autonomous payments pipeline
Pricing
Paid
Pay per call in fixed USDC on Base via x402; no account needed.
Prices change. Check brainiac.software before you buy.
BRAINIAC Card Payments, SCA & APP Scam Rules FAQ
Do I need an account to use BRAINIAC Card Payments, SCA & APP Scam Rules?
The vendor site says there is no account to set up; payment is made per call in USDC on Base.
What happens if I call a tool without paying?
The server returns HTTP 402, as stated in the registry entry.
What currency is used?
Calls are priced in fixed USDC on Base, according to the vendor site.
Is BRAINIAC Card Payments, SCA & APP Scam Rules free?
No. BRAINIAC Card Payments, SCA & APP Scam Rules is a paid product.
How do I add BRAINIAC Card Payments, SCA & APP Scam Rules to Claude Code?
Run this command in your terminal: claude mcp add --transport http card-payments https://www.brainiac.software/mcp/card-payments
What are the best alternatives to BRAINIAC Card Payments, SCA & APP Scam Rules?
The closest alternatives to BRAINIAC Card Payments, SCA & APP Scam Rules are BRAINIAC Bank Account Identifiers & Payment Files, BRAINIAC Accounts Payable, BRAINIAC Agent Execution Contract Intelligence, BRAINIAC Application & Pipeline Security Checks and BRAINIAC Account Abstraction.
Where this comes from
- Description: written from the project's website and its MCP Registry entry.
- Status and tools: checked automatically by AIPoweredBot on 21 November 2026.
- Install steps: from the official MCP Registry entry.