{
  "markdown": "# FDIC — Bank Health and Financials\n\nThe Federal Deposit Insurance Corporation's BankFind and Call Reports data. Quarterly Call Report financials for every FDIC-insured bank in the US (~4,500 institutions), plus failed bank lists, branch maps, and supervisory designations. Free, no auth.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Why this matters for AI agents\n\nFor bank-level due diligence, deposit-flight risk monitoring, or \"is this regional bank in trouble?\" questions, FDIC Call Report data is the source. It's how the FDIC and Fed themselves measure bank health: capital ratios, loan delinquencies, deposit composition, asset quality.\n\nCommon flows:\n\n- **Bank lookup.** Find a specific institution by name or RSSD ID, get its key financials.\n- **Health snapshot.** Capital adequacy ratios (Tier 1, leverage), nonperforming loan rates, allowance coverage, asset/deposit growth.\n- **Regional / sector aggregation.** Aggregate by state, asset size class, or business model (community, regional, money-center).\n- **Failure / merger history.** Search the FDIC's failed bank list (since 2000) for context on regional patterns.\n\nUsed by the `fintech_bank_health_check` compound.\n\n## Auth\n\nNone. FDIC's BankFind and Call Report APIs are fully public, free, no key.\n\n## Update cadence\n\nBanks file Call Reports quarterly with a regulatory deadline of ~30 days after quarter-end. Public release follows within a few additional weeks. So Q1 data publicly visible by mid-May, Q2 by mid-August, etc. Pipeworx caches with TTLs aligned to release windows.\n\n## Bank identifiers\n\n| ID | What it is |\n|---|---|\n| **RSSD ID** | Federal Reserve's primary bank identifier (Replication Server System for Data); stable across name changes |\n| **CERT** | FDIC's certificate number; insurance identifier |\n| **FFIEC ID** | Used in Call Reports |\n\nFor cross-source linking (Fed + FDIC + OCC), RSSD ID is the canonical key. Use it whenever you have a choice.\n\n## Common pitfalls\n\n- **Call Report consolidation level.** Reports come at the bank-holding-company (BHC) level OR the individual-bank level. They don't aggregate cleanly — totals at one level can differ from sums at the other due to inter-affiliate transactions.\n- **Non-FDIC institutions.** Credit unions are NCUA-regulated, not FDIC. They don't appear here. Investment banks (without an insured depository subsidiary) also don't.\n- **Failed banks vs. unwound banks.** FDIC failure list = formal receivership. Other institutions exit the industry via voluntary liquidation, merger, or charter conversion — those don't appear as \"failed.\"\n- **Capital ratio interpretation.** A bank's Tier 1 ratio of 11% is fine in normal times but stretched if loan losses spike. Look at trend, not just snapshot.\n- **Deposit concentration.** \"Uninsured deposits\" (>$250k) is a critical risk metric. Find it in the call report; raw \"total deposits\" alone misses the deposit-flight-risk story (cf. SVB).\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"fdic\": {\n      \"url\": \"https://gateway.pipeworx.io/fdic/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/fdic/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Fdic data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 5013,
  "sha": "fffda61bcad51c83d37f2a40fc586561e92411a02721ea0377fa4010eaac3886",
  "repo_slug": "pipeworx-io/mcp-fdic",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_fdic_5b0ad1f8/readme"
}