fdic-banks-mcp-server

Search FDIC-insured institutions

fdic_search_institutions

Read-onlyIdempotent

Find FDIC-insured banks and savings institutions by name, CERT, location, size, charter class, or holding company — including closed, merged, and failed institutions. Name matching is fuzzy, case-insensitive, and also matches former and trade names (a result says which it matched); every word must match. Returns institution records keyed by CERT, the FDIC certificate number every other fdic_ tool takes, with active status, successor CERT for merged or failed institutions, holding company, and latest reported assets and deposits. Credit unions are insured by the NCUA and are not in this data.

Input Schema

Name	Required	Description
`city`	No	Headquarters city as FDIC spells it (e.g. Seattle, St. Louis), up to 50 characters; matched exactly, as given or in title case, with a hyphen, apostrophe, or space between words also tried the other ways FDIC records it (Winston-Salem finds Winston Salem, Coeur d'Alene finds Coeur D Alene).
`name`	No	Institution name to match, up to 100 characters — current, former, or trade name, case-insensitive, every word required (e.g. "silicon valley"). Punctuation other than & ' . , - is ignored, and so is a standalone N.A. or NA, which then also matches "National Association".
`sort`	No	relevance (active institutions whose current name holds every word of name first, then every other match, each by match score; default when name is given — without name it falls back to assets_desc), assets_desc (largest first; the default otherwise), or name (A–Z).
`certs`	No	Nonempty CERT selection, at most 1000 raw items. Deduplicated first; the first 50 are queried and the rest returned as deferred_certs. missing_certs covers only processed_certs.
`limit`	No	Institutions per page; accepts 1–10000, executes at most 100. effective_limit reports the applied count; use next_offset to continue.
`state`	No	Headquarters state: two-letter code in any case (wa) or full name (Washington); DC and territories accepted.
`offset`	No	Matches to skip (0–100,000); pass next_offset from the previous page.
`status`	No	active, inactive (merged, failed, or closed), or any. Default: any when name or certs is given, otherwise active. The applied value is echoed as status_filter.
`max_assets`	No	Maximum latest reported total assets, in thousands of US dollars.
`min_assets`	No	Minimum latest reported total assets, in thousands of US dollars (1000000 = $1 billion).
`bank_classes`	No	Charter classes to include: N national bank, NM state nonmember bank, SM state member bank, SB federal savings bank, SI state savings bank, SL state savings and loan, OI insured branch of a foreign bank, NC noninsured non-deposit trust company.
`holding_company_rssd`	No	Holding company RSSD ID from any result's holding_company.rssd; lists the institutions under that top holder. With status any, former subsidiaries are included under the holder they had at closing.

Output Schema

Name	Required	Description
`cap`	No	The limit applied to this page.
`error`	No	Present when the call failed. Absent on success.
`shown`	No	Institutions returned on this page.
`total`	No	Institutions matching the filters across all pages.
`notice`	No	Guidance when nothing matched, the page is past the end, or more pages remain.
`truncated`	No	True when more matches remain beyond this page.
`data_as_of`	No	When FDIC last rebuilt the institutions index (ISO timestamp).
`next_offset`	No	Offset of the next page; present when more matches remain.
`institutions`	No	Matching institutions for this page.
`missing_certs`	No	Requested CERTs that match no institution record.
`status_filter`	No	The status filter applied.
`deferred_certs`	No	CERTs not queried; pass these as certs (peer_certs for comparisons) in a new call.
`effective_limit`	No	Page size applied, at most 100.
`processed_certs`	No	Deduplicated CERT selection actually queried; missing CERTs are a subset of these.
`selection_notice`	No	Execution caps and how to retrieve deferred selections.

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedOct 16, 2026

changedInput schema / properties / bank_classes / maxItems
```
Previous value: -8New value: +1000
```
addedInput schema / properties / bank_classes / minItems
```
Added value: +1
```

changedInput schema / properties / certs / description

Previous value: -"Exact lookup by up to 50 CERTs; requested CERTs with no record come back in missing_certs."New value: +"Nonempty CERT selection, at most 1000 raw items. Deduplicated first; the first 50 are queried and the rest returned as deferred_certs. missing_certs covers only processed_certs."

changedInput schema / properties / certs / maxItems
```
Previous value: -50New value: +1000
```
addedInput schema / properties / certs / minItems
```
Added value: +1
```

changedInput schema / properties / limit / description

Previous value: -"Institutions per page (1–100)."New value: +"Institutions per page; accepts 1–10000, executes at most 100. effective_limit reports the applied count; use next_offset to continue."

changedInput schema / properties / limit / maximum
```
Previous value: -100New value: +10000
```

addedOutput schema / properties / deferred_certs

Added value: +{
+  "description": "CERTs not queried; pass these as certs (peer_certs for comparisons) in a new call.",
+  "items": {
+    "description": "Deferred CERT.",
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  "type": "array"
+}

addedOutput schema / properties / effective_limit

Added value: +{
+  "description": "Page size applied, at most 100.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

addedOutput schema / properties / processed_certs

Added value: +{
+  "description": "Deduplicated CERT selection actually queried; missing CERTs are a subset of these.",
+  "items": {
+    "description": "Processed CERT.",
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  "type": "array"
+}

addedOutput schema / properties / selection_notice

Added value: +{
+  "description": "Execution caps and how to retrieve deferred selections.",
+  "type": "string"
+}

First observedOct 9, 2026

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only cover read-only/idempotent/open-world; the description adds substantial behavior the agent could not infer: fuzzy, case-insensitive, word-required name matching, matching against former and trade names with the result indicating which matched, and successor CERT for merged/failed institutions. That is exactly the kind of disclosure that prevents wrong calls.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, front-loaded with purpose, then matching semantics, then return shape, then the exclusion caveat. No filler, and each sentence carries distinct information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description need not enumerate return fields, yet it briefly orients the agent (CERT key, status, successor CERT, assets/deposits). Combined with annotations covering the safety profile and a fully documented schema, nothing required to select or invoke this tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds cross-tool semantics — that records are keyed by CERT and that this CERT is the identifier every other fdic_ tool accepts — plus reinforces the name-matching semantics that govern the name parameter. The remaining parameters (sort, limit, offset, asset bounds) are left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Find) and resource (FDIC-insured banks and savings institutions) plus the searchable facets — name, CERT, location, size, charter class, holding company. It also explicitly scopes what is excluded (credit unions under NCUA), which cleanly separates it from siblings like fdic_search_failures and fdic_get_institution_financials.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context for when this is the right tool — broad institution lookup across active and closed/merged/failed entities — and notes that CERT is the join key every other fdic_ tool consumes, which helps chaining. It stops short of naming an explicit alternative (e.g., use fdic_search_failures for failure-event data), so routing is inferred rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All fdic-banks-mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.