FDIC BankFind MCP Server

io.github.jflambPublished by GitHub account jflambv3.0.1Updated Oct 24, 2026

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

The publisher's own server: Verified Codes

VerifiedSTDIODesktop onlyFinanceData & Analytics

Overview

AI-generated overview

A local MCP server that lets an assistant search FDIC bank institutions, branches and failures and run peer comparisons.

What you can do
Search FDIC-insured financial institutions. Look up bank branches and locations. Review bank failure records. Run peer comparison analysis.
When to use it
Use it when you need to look up US banks, branches, failure records or peer comparisons and want the assistant to pull FDIC public data directly in conversation. Suited to financial research, compliance checks or market analysis.
Requirements
Runs locally as the npm package fdic-mcp-server over stdio, so Node.js is needed. Requires network access to FDIC public data services. No account or API key is declared.
Before you install
The server queries public FDIC data and appears read-only, but results should still be checked for timeliness and accuracy before being relied on for investment or compliance decisions.

Installation

In SourceWeft

  1. Open FDIC BankFind MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v3.0.1LatestSep 18, 2026
  2. v1.30.2Sep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Find integrations