Fin Codes API

com.fincodesapiPublished by fincodesapi.comOfficial publisherv1.0.1Updated Oct 29, 2026

Validate IBANs and bank codes, verify payee names, and screen names against sanctions lists.

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

Hosted MCP server for banking reference data: validate IBANs and national bank codes, verify payee names, and screen names against sanctions lists.

What you can do
  • Validate IBANs and return bank, country and BIC/SWIFT details, and compare a payee name with the holder of a supported European IBAN
  • Resolve BIC/SWIFT bank and branch details
  • Look up national bank codes: US ABA routing numbers, Canadian routing numbers, Australian BSB, New Zealand bank and branch codes, Indian IFSC
  • Validate Mexican CLABE and Argentine CBU codes and identify their banks
  • Screen a name against EU, UK, UN, OFAC, Swiss, Australian and Canadian sanctions lists
When to use it
Useful when an assistant needs to check bank details in documents, invoices or onboarding forms, confirm that a payee name matches an IBAN, or run a first-pass sanctions name screen. It is a reference-data and screening aid, not a payment or identity-verification system.
Requirements
Remote Streamable HTTP endpoint at mcp.fincodesapi.com; no local package. A Fin Codes API account is required, normally signed in through OAuth; clients without OAuth can use an API key sent as an Authorization Bearer header. Lookups consume plan quota and payee checks consume prepaid credits.
Before you install
Inputs, including names and bank details, are sent to the hosted Fin Codes API service. Lookups consume plan quota and payee checks consume prepaid credits, so usage costs money. If you use an API key instead of OAuth, keep it in the client's secret store and out of shared files. Results are indicative: bank-code validity does not prove account existence or ownership, and sanctions name matches require human review.

Installation

In SourceWeft

  1. Open Fin Codes API in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.fincodesapi%2Ffincodesapi/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "fin-codes-api": {
      "type": "http",
      "url": "https://mcp.fincodesapi.com/mcp"
    }
  }
}

README

Fin 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

sh
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:

json
{"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:

json
{"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

sh
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

ToolPurpose
lookup_ibanValidate an IBAN and return bank, country, and BIC/SWIFT details
verify_iban_payeeCompare a supplied payee name with the holder of a supported European IBAN
lookup_bicResolve BIC/SWIFT bank and branch details
lookup_us_routing_numberLook up a US ABA routing number
lookup_canada_routing_numberLook up a Canadian routing number
lookup_australia_bsbLook up an Australian BSB
lookup_new_zealand_bank_codeLook up a New Zealand bank and branch code
lookup_india_ifscLook up an Indian IFSC
lookup_mexico_clabeValidate a Mexican CLABE and identify its bank
lookup_argentina_cbuValidate an Argentine CBU and identify its bank
screen_sanctionsScreen 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: [email protected] 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.

Source: README.md at commit 5390bf7

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestOct 29, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts