The neobankbeat MCP server
Model Context Protocol is the open standard for connecting AI assistants to tools and data. This server exposes the whole neobankbeat dataset as five tools, so Claude (or any MCP client) can query it directly — every answer traceable to a profile page.
The tools
| search_neobanks | Plain-language search — "European neobanks with stablecoins", "self-custody banks in Brazil". Parses facets + keywords. |
| get_neobank | The full verified record for one neobank — custody, license, cards, yield, stablecoins, KYC, regulation, geography, features, sources. |
| compare_neobanks | Two to four neobanks compared field by field. |
| list_by_country | Neobanks headquartered in / available in a country. |
| dataset_stats | Totals and category breakdown, with the as-of note. |
Install (Claude Desktop)
You need Node.js 18+ and the server file from the repo (mcp/server.mjs). Add this to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/), then restart Claude Desktop:
{
"mcpServers": {
"neobankbeat": {
"command": "node",
"args": ["/absolute/path/to/neobankbeat/mcp/server.mjs"]
}
}
}
The neobankbeat tools then appear. Any MCP client that speaks the stdio transport works the same way — point it at node mcp/server.mjs. Full setup notes in the README.
Why it's useful
AI assistants answer questions about neobanks constantly — "which neobank has an API?", "compare Mercury and Brex", "self-custody options in Europe" — and get them wrong or stale from training data. Pointed at this server, the model answers from the current, verified dataset, cites the profile page behind each fact, and respects the null = unverified rule rather than inventing a "no". It reads the live data.json, so it is never out of date.
Figures compiled from public sources, for comparison only — not financial advice. "Up to" rates change constantly; always confirm with the issuer. Spotted an error? Suggest a fix.