Fin Codes API MCP server
Commit Oct 29, 2026Validate IBANs, bank codes, and payee names while screening individuals against global sanctions lists.
Also known as swiftcodesapi/fincodesapi-mcp, fincodesapi-mcp
- Stars
- 0
- Tools
- 11
- Downloads, 30 days
- —
- Latest version
- 1.0.1
- Last commit
- Oct 29, 2026
- License
- MIT
What is Fin Codes API MCP?
Fin Codes API validates IBANs, bank codes, and payee names while screening individuals against global sanctions lists. It exposes 11 tools, such as lookup_iban, verify_iban_payee, lookup_bic.
Summary generated from the project's README
About Fin Codes API MCP server
Fin Codes API provides a remote MCP server that connects AI assistants to global banking reference data and compliance tools. Developers can integrate this service into clients like Claude Code, VS Code, Cursor, Cline, and Gemini CLI using streamable HTTP transport. The server requires a Fin Codes API account, which can be authenticated via OAuth or through a manually created API key for clients that do not support OAuth.
The server provides eleven specialized tools for financial data validation and security. These include functions to lookup IBANs, BIC/SWIFT details, and various regional routing numbers for the US, Canada, Australia, New Zealand, India, Mexico, and Argentina. It also features a tool to screen names against major international sanctions lists, including EU, UK, UN, OFAC, Swiss, Australian, and Canadian registries. Users should note that lookups consume account plan quotas while payee checks use prepaid Verification of Payee credits.
What you can do with it
- 1Validate international bank detailsVerify an IBAN to retrieve its associated bank, country, and BIC information.
- 2Verify regional routing numbersIdentify the specific bank and branch associated with an Australian BSB code.
- 3Perform sanctions screeningCheck a specific name against global sanctions lists to ensure compliance.
- 4Confirm payee name matches IBANCompare a person's name against the holder of a European IBAN to prevent errors.
Written from the project's README. Every use case is checked against a quote from it.
How to install Fin Codes API MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Fin Codes API MCP in Claude Code
$ claude mcp add --transport http fincodesapi-mcp https://mcp.fincodesapi.com/mcpInstall Fin Codes API MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"fincodesapi-mcp": {
"url": "https://mcp.fincodesapi.com/mcp"
}
}
}Install Fin Codes API MCP in VS Code
.vscode/mcp.json
{
"servers": {
"fincodesapi-mcp": {
"type": "http",
"url": "https://mcp.fincodesapi.com/mcp"
}
}
}Install Fin Codes API MCP in VS Code CLI
$ code --add-mcp '{"name":"fincodesapi-mcp","type":"http","url":"https://mcp.fincodesapi.com/mcp"}'Install Fin Codes API MCP in Codex
$ codex mcp add fincodesapi-mcp --url https://mcp.fincodesapi.com/mcpInstall Fin Codes API MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.fincodesapi-mcp] url = "https://mcp.fincodesapi.com/mcp"
Install Fin Codes API MCP in Gemini CLI
$ gemini mcp add -s user --transport http fincodesapi-mcp https://mcp.fincodesapi.com/mcpInstall Fin Codes API MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"fincodesapi-mcp": {
"url": "https://mcp.fincodesapi.com/mcp",
"type": "http"
}
}
}Fin Codes API MCP tools 11
Detected from the READMElookup_ibanverify_iban_payeelookup_biclookup_us_routing_numberlookup_canada_routing_numberlookup_australia_bsblookup_new_zealand_bank_codelookup_india_ifsclookup_mexico_clabelookup_argentina_cbuscreen_sanctions
| lookup_iban | — | |
| verify_iban_payee | — | |
| lookup_bic | — | |
| lookup_us_routing_number | — | |
| lookup_canada_routing_number | — | |
| lookup_australia_bsb | — | |
| lookup_new_zealand_bank_code | — | |
| lookup_india_ifsc | — | |
| lookup_mexico_clabe | — | |
| lookup_argentina_cbu | — | |
| screen_sanctions | — |
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableswiftcodesapi/fincodesapi-mcp is public and reachablegithub.com/swiftcodesapi/fincodesapi-mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-29github.com/swiftcodesapi/fincodesapi-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model11 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubFin Codes API MCP server
Connect your AI assistant to banking reference data, payee-name verification, and sanctions screening.
Hosted endpoint: https://mcp.fincodesapi.com/mcp
Transport: Streamable HTTP
Homepage and setup: https://fincodesapi.com/mcp-server
Official registry: com.fincodesapi/fincodesapi
This repository contains public connector configuration and documentation for the hosted service. It does not contain the proprietary backend, run a local server, or publish an npm, PyPI, or Docker package.
Connect
Add the endpoint as a remote HTTP MCP server in your client, then sign in to your Fin Codes API account through OAuth. Sign up at https://fincodesapi.com/sign-up if needed. OAuth-aware clients do not need a manually created API key.
Claude Code
claude mcp add --transport http fincodesapi https://mcp.fincodesapi.com/mcp
Run /mcp to sign in. In Claude Desktop or claude.ai, add the endpoint as a custom connector.
VS Code
Add to .vscode/mcp.json, then start the server and sign in:
{"servers":{"fincodesapi":{"type":"http","url":"https://mcp.fincodesapi.com/mcp"}}}
Cursor and other MCP clients
Add the remote endpoint in the client's MCP settings. The included mcp.json defines the connection; plugin.json is a portable Agent Plugins manifest. Client support and OAuth setup vary.
Cline
In Cline, open MCP Servers → Remote Servers, add the endpoint above, and choose Streamable HTTP. Complete OAuth authorization when prompted. If using JSON configuration, use Cline's transport spelling:
{"mcpServers":{"fincodesapi":{"type":"streamableHttp","url":"https://mcp.fincodesapi.com/mcp","disabled":false,"autoApprove":[]}}}
If OAuth is unavailable in your client version, create your own API token at https://fincodesapi.com/api-keys and add an Authorization: Bearer YOUR_API_KEY header locally. Keep the key out of shared files. Confirm that eleven tools appear and try looking up BSB 082-024.
See Cline's MCP documentation. Cline installation of this connector has not yet been independently tested.
Gemini CLI
gemini extensions install https://github.com/swiftcodesapi/fincodesapi-mcp
Run /mcp auth fincodesapi if prompted to sign in. The extension uses HTTP transport and OAuth discovery.
API-key clients
Clients without OAuth can use an API key created at https://fincodesapi.com/api-keys. Send Authorization: Bearer YOUR_API_KEY to the same endpoint. Store your real key in the client's secret store; never commit it to this repository.
Eleven tools
| Tool | Purpose |
|---|---|
lookup_iban |
Validate an IBAN and return bank, country, and BIC/SWIFT details |
verify_iban_payee |
Compare a supplied payee name with the holder of a supported European IBAN |
lookup_bic |
Resolve BIC/SWIFT bank and branch details |
lookup_us_routing_number |
Look up a US ABA routing number |
lookup_canada_routing_number |
Look up a Canadian routing number |
lookup_australia_bsb |
Look up an Australian BSB |
lookup_new_zealand_bank_code |
Look up a New Zealand bank and branch code |
lookup_india_ifsc |
Look up an Indian IFSC |
lookup_mexico_clabe |
Validate a Mexican CLABE and identify its bank |
lookup_argentina_cbu |
Validate an Argentine CBU and identify its bank |
screen_sanctions |
Screen a name against EU, UK, UN, OFAC, Swiss, Australian and Canadian sanctions lists |
Live MCP tool schemas are authoritative.
Examples
- “Validate DE57 1001 0010 0593 9081 19 and tell me its bank and BIC.”
- “Which bank and branch does Australian BSB 082-024 identify?”
- “Run the documented free payee verification fixture: does DE75512108001245126199 match John Doe?”
- “Screen the name Sadam Husein with a minimum match score of 95.”
The John Doe/IBAN pair is a documented test fixture. Its response does not establish real account ownership. Bank-code validity alone does not establish account existence or ownership. Sanctions name similarity requires review and does not establish identity or sanctioned status. The tools do not transfer money, execute trades, reverse-search private accounts by name, or determine creditworthiness.
Account and pricing
A Fin Codes API account is required. Lookups consume the account's plan quota; payee checks consume prepaid Verification of Payee credits. Plans and credits are purchased on https://fincodesapi.com/pricing. The connector does not process purchases or payments. A trial is available; current terms and limits are shown on the website.
Privacy and support
Inputs are sent to the hosted Fin Codes API service. Review https://fincodesapi.com/privacy-policy, https://fincodesapi.com/gdpr, and https://fincodesapi.com/terms-of-service before use. Support: andrej@fincodesapi.com or Contact us at https://fincodesapi.com/mcp-server.
License
The connector configuration and documentation in this repository are MIT licensed. The hosted service remains governed by its Terms of Service.
Fin Codes API MCP questions
How do I add Fin Codes API MCP to Claude Code?
Run claude mcp add --transport http fincodesapi-mcp https://mcp.fincodesapi.com/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Fin Codes API MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does Fin Codes API MCP provide?
It exposes 11 tools, including lookup_iban, verify_iban_payee, lookup_bic, lookup_us_routing_number, lookup_canada_routing_number.
How do I connect to the Fin Codes API MCP server?
You can add the endpoint as a remote HTTP MCP server in your client and sign in via OAuth, or use an API key for clients that do not support OAuth.
What tools are available in this server?
The server provides eleven tools including IBAN validation, BIC/SWIFT resolution, US/Canada/Australia/India/Mexico/Argentina routing number lookups, and sanctions screening.
Can I use this server without an account?
No, a Fin Codes API account is required to use the service, and lookups consume your plan's quota or prepaid credits.
Does this server allow me to transfer money?
No, the tools are for data lookup and verification only; they do not execute money transfers or trades.