MCP server
Connect any MCP-compatible AI client to fin.codes' verified routing-number data. Look up and verify routing numbers, search banks, and get the proof — straight from the bank's own page.
Remote endpoint
Streamable HTTP. Hosted MCP clients can add the URL directly; legacy SSE clients can use https://mcp.fin.codes/sse.
endpoint
https://mcp.fin.codes/mcpFor a config-file client (Claude Desktop, Cursor), use mcp-remote:
json · config
{
"mcpServers": {
"fin.codes": {
"command": "npx",
"args": ["mcp-remote", "https://mcp.fin.codes/mcp"]
}
}
}What it exposes
- lookup_routing_number
- The bank, use, and verification for a 9-digit number.
- verify_routing_number
- Is it bank-verified? With the proof.
- lookup_bank
- A bank profile and its routing numbers.
- find_banks
- Search by name, state, or verification.
- lookup_ein
- Who a 9-digit EIN belongs to, with how it was sourced.
- find_eins
- An organization's EIN by name or number prefix.
- get_wire_fees
- Published wire fees from each bank's own fee schedule.
- explain_topic
- ACH vs wire, how we verify, and more.
Free tier and commercial use
The MCP server is rate-limited (30 requests/min per IP). Building a product on it, or need higher limits and commercial terms? Contact us.