SiteCheck Crypto & Finance

US FDIC-insured banks: name, FDIC cert, Fed RSSD ID

finance_ffiec_bank_institutions

Read-only

US FDIC-insured banks (FDIC BankFind call-report data): name, FDIC cert, Fed RSSD ID, location, total assets, deposits and net income (USD), ROA and ROE, report date, charter class, regulator, office counts, holding company, website, established date, active flag and closing date. Search by name, filter by state and active status, sort by assets, deposits, name or age; or look up one bank by cert. Related tools on this server, for a different need: finance_fdic_bank when you need FDIC-insured bank institutions in one US state; finance_asian_dev_bank_data when you need Asian Development Bank financing from ADB's official IATI. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "finance_ffiec_bank_institutions"
  }
}

Input Schema

Name	Required	Description
`cert`	No	Optional FDIC certificate number for one bank
`name`	No	Optional words of the bank name, e.g. Chase, Frost
`page`	No	Page number from 1 (default 1)
`sort`	No	assets (default), deposits, name or established
`limit`	No	Banks to return, 1 to 100 (default 25)
`state`	No	Optional 2-letter state, e.g. TX
`active`	No	true (default) for active banks, false for closed/merged ones, all for both

Output Schema

Name	Required	Description	Default
`page`	No
`banks`	No
`count`	No
`query`	No
`total`	No
`source`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the x402 payment model ($0.002 USDC per successful call, failed calls not charged) and the source dataset. It stops short of describing pagination limits or result ordering beyond the sort parameter.

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

Conciseness4/5

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

Front-loads the resource and its fields, then operations, then alternatives, then pricing — a sensible order. The field enumeration is long but each item is a genuine output column; no filler sentences.

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?

For a read-only search tool with a full-coverage schema, annotations, and an output schema, the description covers everything an agent needs: what is returned, how to query, when to prefer a sibling, and the paid-call mechanism.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter is already documented, and the description largely restates those same filters and sort keys. It adds one small mapping ("age" corresponds to the schema's established sort) and confirms cert is used for single-bank lookup, but supplies no format or combination rules the schema lacks.

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?

Opens with a specific resource (US FDIC-insured banks from FDIC BankFind call-report data) and enumerates the returned fields, then states the concrete operations: search by name, filter by state/active status, sort, or look up one bank by cert. It explicitly separates itself from the sibling finance_fdic_bank, so an agent can choose without opening either schema.

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 usage context (search/filter/sort vs single-bank lookup by cert) and names two alternatives with the condition that selects them. The distinction against finance_fdic_bank is slightly muddy since both accept a state filter, but the routing hint is explicit rather than implied.

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

All SiteCheck Crypto & Finance 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.

Resources

Need Help?