Payment Intelligence MCP server
io.github.Raafet57/payment-intelligence·v0.3.2Offline ISO 20022 payment tools: explain and scrub pacs/camt, CBPR+, SSI checks, IBAN and BIC.
0 stars412 downloads/wk
Reviews
Write oneNobody has reviewed Payment Intelligence yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Payment Intelligence tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-25 · same rubric, same numbers if you re-run it
- Code scan65 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 3 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Payment Intelligence compares
Against every graded Finance MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 95% of 1,761 Finance servers
- Downloads a week
- 412
- more than 90% of 421 Finance servers with a package
Release history: 2 versions in the registry since 2026-10-22, latest 2026-10-25, typically one every 3 days.
Install Payment Intelligence in Claude Code, Cursor or VS Code
Runs npx -y payment-intelligence-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add payment-intelligence -- npx -y payment-intelligence-mcp
What the publisher says
From the Payment Intelligence repository's README, as published. We do not edit it. Read it on GitHub
Payment Intelligence: ISO 20022 tools for AI assistants
Offline ISO 20022 tools for payment operations, investigations and migration teams, packaged for Claude Code, OpenAI Codex, GitHub Copilot, VS Code, Gemini CLI, Cursor and any MCP client. It is built on the same libraries as the Payment Intelligence Modules browser suite.
Nothing leaves your machine. The plugin runs a local MCP server over stdio. It makes no network calls, sends no telemetry and has no account. It only reads files you name, and writes only the scrubbed copy you ask for.
We don't provide reference data. The plugin works on your own. No SwiftRef, BIC Directory or SSI data is shipped, sold or downloaded. Your institution already licenses that data; the tools read the files you point them at, on your machine: your own reference files, your own SSI file and your own payment messages. It is provider-agnostic:
- SWIFTRef, current format: unzipped BIC Directory and Payments Directory folders (IDENTIFIERS including historical, PARTICIPANTS and RELATIONSHIPS files; layouts are read from the STRUCTURES file in the same download).
- SWIFTRef, legacy products: BIC Plus, BIC Directory 2018, Bank Directory Plus, IBAN Plus, SEPA routing, Reach Plus, gpi, and SSI Plus.
- Any other provider or in-house system: CSV/TSV exports. Common column names are recognised automatically, column_map covers any other layout, and any column it cannot map is listed in the result, so there is no lock-in to one data vendor.
The only data built in is public format rules: the SWIFT IBAN Registry structures, ISO country and currency codes, and a short list of ISO status and reason codes.
What you can ask
- "Explain this pacs.008 / pacs.004 / camt.053."
- "Scrub payments/batch-0412.xml before I send it to the vendor."
- "Why was this payment returned? Here are the pacs.008, pacs.002 and pacs.004."
- "Here is the camt.110 we received and the original pacs.008. What are they asking, and has it been answered?"
- "What did the responder confirm in this camt.111?" or "What do these Tracker notifications say about our case?"
- "Is DE89 3704 0044 0532 0130 00 a valid IBAN?" or "Build a French IBAN from these bank and account numbers."
- "Is this message CBPR+ ready?"
- "Validate our SSI file ssi/master.tsv." or "Does this pacs.009 pay Nova through the correspondent in our SSI file?"
- "Look up DEUTDEFF in our BIC Directory at ~/swiftref/2026-02." or "Which BIC does sort code 400501 route to?"
- "Check this pacs.009 against the SSIs in our Payments Directory RELATIONSHIPS file."
Components
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Payment Intelligence: common questions
- Is Payment Intelligence MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the Payment Intelligence safety report
- How do I install Payment Intelligence?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Payment Intelligence need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Payment Intelligence maintained?
- The last commit was 13 days ago (2026-10-22). The latest release is v0.3.2.
- What can I use instead of Payment Intelligence?
- Servers from other publishers that do the same job: Ibanforge MCP server, Yolfi Payments MCP server and Pulsefeed X402 MCP server. Compare all Payment Intelligence alternatives.
- How does Payment Intelligence compare with other Finance MCP servers?
- safety score 92/100 (higher than 95% of 1,761 Finance servers); downloads a week 412 (more than 90% of 421 Finance servers with a package). Full comparison.
Alternatives to Payment Intelligence
Same job from other publishers: the closest match first, then the best rated.
IbanforgeCheck the bank behind an IBAN before you pay: bank-code check, BIC with source, bank-level sanctionsnot reviewedGrowingB- Yolfi Payments MCPLet AI agents add Yolfi crypto checkout, paylinks, webhooks, and status checks.not reviewedEstablishedA
- Pulsefeed X402Verify x402 payment endpoints before an AI agent pays: scam scan, on-chain checks, trust scores.not reviewedGrowingA
- three.ws Agent PaymentsGoverned x402 payment sessions: pay any endpoint with budget, allowlist & per-tx caps, no key.not reviewedEstablishedB
Hive Intelligence MCPEvidence-backed crypto due diligence with sources, freshness, and a runtime receipt on every call.not reviewedEstablishedC