Plug US banking data
into your AI.
Our MCP server turns the BankRegReports API into native tools for Claude, Cursor, VS Code, and any MCP client. Ask in plain English, “How’s First Republic’s capital trending?”, and the model fetches live Call Report, scorecard, peer, and failure data itself.
# "What are JPMorgan's capital ratios?" # → the model calls: { "name": "bank", "arguments": { "rssd_id": "852218" } } # ← structured result { "cet1_ratio": 15.08, "tier1_ratio": 16.61, "total_capital_ratio": 18.30 }
Connect your client
The server speaks Streamable HTTP at https://api.bankregreports.com/api/mcp/. Point any MCP client at it.
claude mcp add --transport http \ bankregreports \ https://api.bankregreports.com/api/mcp/
Open Settings, then Connectors, then Add custom connector. Name it BankRegReports, paste the URL, and select Connect. No mcp-remote bridge is needed.
That’s it: anonymous access to this free endpoint covers every public dataset. To also reach free-tier datasets (scorecards, failure-risk scores, SEC filings), send a free API key as a bearer header (Authorization: Bearer brr_your_free_key) from a client that supports custom headers.
Have a Pro or Scale plan? Sign in instead.
The sign-in connector at https://mcp.bankregreports.com/mcp uses your BankRegReports account, with one-click setup for Claude and steps for Cursor, VS Code and ChatGPT.
What the model can do
Every public & free dataset is exposed as a tool, 114 in all, kept in lock-step with the REST API. With a key, the model can also read your watchlist and saved graphs. A few examples:
Look up a bank
“Find banks in Georgia over $1B in assets” → screener, then bank for the snapshot.
Track a trend
“How have deposits moved over 12 quarters?” → bank_trends.
Judge safety
“Is this bank at risk?” → scorecard + prediction (free key).
Watch the industry
“Recent failures and enforcement?” → failures_recent, enforcement.
Built to stay cheap & safe
Read-only
Every tool is a GET. No writes, no account changes, nothing the model can break.
Cache-first
Tool calls reuse the same cache the site runs on, so popular questions don’t touch the warehouse.
Rate-limited
A generous per-minute limit keeps runaway agents polite; a hard daily cost ceiling protects the rest.
Tiered access
Public data needs no key; a free key unlocks free datasets, and a Pro key adds the Pro datasets. Every dataset is also on the REST API.