# FDIC Bank Diligence MCP Server (`nexgenwatch/fdic-bank-diligence-mcp`) Actor

Answer questions about US banks from the FDIC's public data: institution details, structural history, current status, closures and failures - for vetting a bank counterparty.

- **URL**: https://apify.com/nexgenwatch/fdic-bank-diligence-mcp.md
- **Developed by:** [NexGen Watch](https://apify.com/nexgenwatch) (community)
- **Categories:** Agents, Business
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $50.00 / 1,000 tool calls

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## FDIC Bank Diligence MCP Server

Answer questions about **US banks** from the FDIC's public BankFind data — institution
details, structural history, current status, closures and failures — live, for vetting a
bank counterparty.

### Four things this server gets right that a naive read gets wrong

Every one measured live against the source on 2026-07-30.

#### 1. The source states its own rate limit, and it is one request per second

Every FDIC response carries `x-ratelimit-limit: 1`. During the pre-gate a burst of queries
earned a real **HTTP 429**. This server paces at **1 request/second** — five times slower
than the other JSON servers in this family, because the source says so — and treats a 429
as a temporary failure that **charges nothing**.

A 429 is never an answer. "No such bank" is HTTP 200 with a total of 0, and that is
different.

#### 2. `12/31/9999` is a sentinel meaning "no end date", and it poisons a naive sort

Ask for the most recently closed institutions the obvious way — inactive, sorted by end
date, descending — and the FDIC returns:

```
12/31/9999  Wells Fargo Trust Company, National Association
12/31/9999  Fiduciary Trust Company International
12/31/9999  Fidelity Management Trust Company
```

Three institutions that **never closed**, sitting at the top of a list of closures. **26 of
the 23,581 inactive records carry the sentinel.** Exclude it and the answer is right:

```
2026-07-17  Small Business Bank
2026-07-10  Kentland Federal Savings and Loan Association
2026-07-01  Zapata National Bank
```

This server excludes the sentinel **at the query** and converts it to `null` **at the
parser**, so it cannot reach a sort, a comparison, or your screen as a real date.

#### 3. Three date formats in one API

```
institutions   ESTYMD / INSDATE / ENDEFYMD   "01/01/1870"           MM/DD/YYYY
history        EFFDATE                       "1910-01-20T00:00:00"  ISO with a T
failures       FAILDATE                      "5/1/2026"             M/D/YYYY, unpadded
```

All three go through one parser that returns ISO or `null`, and never guesses.

#### 4. An unknown field name is silently dropped — no error

Measured: `fields=NAME,NOT_A_REAL_FIELD` returns HTTP 200 and a row containing only `NAME`.
A typo does not fail; it quietly returns an answer with a hole in it. So field lists here
are **fixed constants** and the caller cannot choose them.

### Tools

| tool | what it answers |
|---|---|
| `find_bank` | Institutions matching a name, each with its FDIC certificate number |
| `get_bank` | Everything published about one institution — status, charter class, regulator, dates, assets, deposits, plus its failure record if it has one |
| `get_bank_history` | Structural history newest first: name changes, mergers, acquisitions, relocations |
| `list_recent_failures` | Failed institutions, with resolution type and estimated cost to the insurance fund |
| `list_recent_closures` | Institutions that ceased to exist — usually a merger, not a failure |
| `explain_limits` | What this server will and will not say, and the four traps above. Read before acting. |

**The FDIC certificate number is the identity.** Names repeat, change and merge; the cert
does not.

### Scope

**FDIC-insured US institutions only.** Credit unions (NCUA-insured), uninsured entities,
non-US banks other than insured US branches, and any supervisory or CAMELS rating are
outside it — supervisory ratings are not public data.

All money figures are in **thousands of US dollars**, as the FDIC publishes them. A total
of `1,852,239,000` means $1.852 trillion.

`banks.data.fdic.gov/robots.txt` is 404 — no rules on the API host — but the API states its
own limit and this server obeys it.

This server reports what the FDIC publishes. It does **not** rate a bank, does **not**
assess creditworthiness, and does **not** say a counterparty is safe.

### Pricing

| Event | Price |
|---|---|
| Server start (`apify-actor-start`) | $0.05, charged once per server run by the platform |
| Tool call (`mcp-tool-call`) | **$0.05 flat per completed tool call** |

No other events. Memory is pinned to 1024 MB so the start fee is charged **once** — on this
platform the start event bills once per gigabyte.

**Errors and notices are not charged.** A malformed certificate number, an empty name, or an
FDIC read failure — **including an HTTP 429 throttle** — returns without billing.

**A sourced "no such institution" IS charged**, and so is a search that matches nothing —
those are the answers to the questions asked.

If a tool call cannot be billed correctly, **the call fails** rather than serving free.

# Actor input Schema

## `note` (type: `string`):

This Actor runs as an MCP server in Standby mode. Connect an MCP client to the server URL with path /mcp; there is no batch input to fill in.

## Actor input object example

```json
{
  "note": "standby"
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "note": "standby"
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgenwatch/fdic-bank-diligence-mcp").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "note": "standby" }

# Run the Actor and wait for it to finish
run = client.actor("nexgenwatch/fdic-bank-diligence-mcp").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "note": "standby"
}' |
apify call nexgenwatch/fdic-bank-diligence-mcp --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgenwatch/fdic-bank-diligence-mcp"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/CAP4Z0gbVlX0S7iMn/builds/daPv4kCVJQMlSuCtY/openapi.json