Should my agent depend on the MCP server io.github.jflamb/fdic-mcp-server?

Verdict: allow — mid-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

FDIC BankFind MCP Server

io.github.jflamb/fdic-mcp-server

Search FDIC institutions, branches, failures, and peer analysis over MCP.

— the operator's own registry description reported

Publisher io.github.jflamb · first seen 2026-08-12 · endpoint https://bankfind.jflamb.com/mcp

allow

verdict

mid-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — mid-solo — safe to depend on

Cluster mid-solo · distinctiveness 0.493 (moderate). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency101 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools29

vs populationmid

capabilities3

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_e51e81ffe533eb549f88d9ed · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

fdic_analyze_bank_health fdic_analyze_credit_concentration fdic_analyze_funding_profile fdic_analyze_securities_portfolio fdic_compare_bank_snapshots fdic_compare_peer_health fdic_detect_risk_signals fdic_fetch fdic_franchise_footprint fdic_get_institution fdic_get_institution_failure fdic_holding_company_profile fdic_market_share_analysis fdic_peer_group_analysis fdic_qbp_lite_data fdic_regional_context fdic_search fdic_search_demographics fdic_search_failures fdic_search_financials fdic_search_history fdic_search_institutions fdic_search_locations fdic_search_sod fdic_search_summary fdic_show_bank_deep_dive fdic_ubpr_analysis fetch search

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	29/29	✓
has a description	29/29	✓
description is substantive	29/29	✓
parameters are typed	29/29	✓
parameters are described	29/29	✓

29 of 29 tools graded · 29 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

1.30.2

server version fdic-mcp-server

Capabilities: prompts resources tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:59:39Z	ok_tools	200	101	2025-06-18
2026-08-12T05:34:52Z	ok_tools	200	92	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.jflamb/fdic-mcp-server.svg)](https://robinsaige.com/s/io.github.jflamb/fdic-mcp-server)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview