fdic-mcp-server

library1.23.2jsnpmunverified

The `fdic-mcp-server` package provides an MCP (Model Context Protocol) server designed to interface with the FDIC BankFind Suite API. It enables AI agents and LLM hosts to programmatically access and analyze public banking records, including information on FDIC-insured institutions, bank failures, branch data, quarterly financials, and deposit statistics, without requiring custom API integration. The current stable version is 1.23.2, with active development indicated by frequent bug fix and feature releases, often multiple times a week as seen in the recent changelog. Its key differentiators include exposing BankFind datasets as MCP tools, preserving both human-readable and machine-readable responses, offering server-side analysis helpers for multi-bank comparison, and supporting both local stdio and remote HTTP hosts. It aims to provide a stable tool surface and machine-readable responses for complex financial queries.

llm-agents data

npm install fdic-mcp-server

github ↗package ↗

INSTALL

IMPORT

SIG · FDIC-MCP-SERVER

fdic-mcp-server

llm-agentsjavascriptv1.23.2

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

fdic-mcp-server (CLI)

✓ npx fdic-mcp-server

✗ import { Server } from 'fdic-mcp-server';

This package is a server application, not a library for direct JavaScript import. It is primarily executed as a command-line tool. 'npx' is the recommended way to run it without a global install.

fdic-mcp-server (Global Install)

✓ npm install -g fdic-mcp-server fdic-mcp-server

✗ require('fdic-mcp-server').start();

For long-term or frequent use, global installation provides a convenient command-line executable. Direct programmatic control via 'require' is not the intended interaction pattern.

fdic-mcp-server (Local Execution)

✓ node dist/index.js

✗ import * as fdicServer from 'fdic-mcp-server/dist/index.js';

When running from a local clone or build, the compiled JavaScript entry point is executed directly with Node.js. Avoid treating 'dist/index.js' as a library module to import into other applications.

This quickstart demonstrates how to run the `fdic-mcp-server` locally using `npx` with HTTP transport and provides a minimal example of how an MCP client would configure access to it, either via command execution or a remote URL.

npx fdic-mcp-server --transport=http --port=3000 & # Wait for the server to start... # Example MCP client configuration (e.g., in a host's config.json): const mcpConfig = { "mcpServers": { "fdic": { "command": "npx", "args": ["-y", "fdic-mcp-server"] }, "fdic_http": { "url": "http://127.0.0.1:3000/mcp" } } }; console.log('MCP server running and configured. You can now use an MCP client to interact with it.');

fdic-mcp --version

Debug

Known issues

breakingThe server explicitly requires Node.js version 20 or later. Running with older versions will result in execution errors.

fix

Upgrade your Node.js environment to version 20.0.0 or higher. Use 'nvm' or similar version managers for easier switching.

affects: <=1.x

gotchaThe package is designed as a server, not a library. Attempting to 'import' or 'require' symbols from it into another JavaScript application for direct programmatic control is not the intended use case and will likely fail or lead to unexpected behavior.

fix

Interact with `fdic-mcp-server` as an external process (via command line) or through its HTTP endpoint using an MCP-compatible client, as shown in the quickstart and usage examples.

affects: >=1.0.0

gotchaBy default, the HTTP transport binds to `127.0.0.1`. If you need to access the server from a different host or specific network interface, you must explicitly set the `HOST` environment variable.

fix

Set the `HOST` environment variable before running the server, e.g., `HOST=0.0.0.0 PORT=3000 node dist/index.js` for all interfaces.

affects: >=1.0.0

gotchaBrowser-origin requests to the HTTP server are subject to `ALLOWED_ORIGINS` checks. If not explicitly configured, it allows only `localhost` and `127.0.0.1` on the configured port, plus non-browser requests without an Origin header.

fix

If serving to browser-based clients from different origins, set the `ALLOWED_ORIGINS` environment variable to a comma-separated list of allowed URLs (e.g., `ALLOWED_ORIGINS=https://my-app.com,http://another-host:8080`).

affects: >=1.0.0

gotchaThe default maximum FDIC response size guard is 5 MiB (`5242880` bytes). Large queries that exceed this limit might be truncated or fail.

fix

If you anticipate very large responses, override this limit by setting the `FDIC_MAX_RESPONSE_BYTES` environment variable to a higher value (e.g., `FDIC_MAX_RESPONSE_BYTES=10485760` for 10 MiB).

affects: >=1.0.0

Errors

Common errors & fixes

Error: The 'fdic-mcp-server' package requires Node.js version 20.0.0 or higher. You are running vX.Y.Z.

Running the server with an unsupported Node.js version.

fix

Update Node.js to version 20.0.0 or newer. Consider using 'nvm' for easy version management.

Error: listen EADDRINUSE: address already in use :::3000

Another process is already using the specified HTTP port (default 3000 or 8080 for containers).

fix

Change the `PORT` environment variable to an unused port (e.g., `PORT=4000 npx fdic-mcp-server`) or terminate the conflicting process.

mcpServers.fdic.command: npx, args: [-y, fdic-mcp-server] -- Command not found or executable permission denied.

The MCP client host cannot find or execute the `npx` or `fdic-mcp-server` command in its environment.

fix

Ensure `npm` (and thus `npx`) is installed and in the system's PATH. If using a local clone, verify the `command` and `args` point to the correct `node` executable and `dist/index.js` path.

TypeError: fetch failed

Often indicates network issues, incorrect server URL, or the `fdic-mcp-server` not running when an MCP client tries to connect via HTTP.

fix

Verify the `fdic-mcp-server` is running, its HTTP endpoint URL is correct (e.g., `http://127.0.0.1:3000/mcp`), and there are no firewall or network connectivity issues.

Upgrade

Version history

1.23.2latest on npm

Audit

Dependencies

No dependency data recorded yet.

Agent activity

18 hits · last 30 days

node

OpenAI (training)

Resources

githubhttps://github.com/jflamb/fdic-mcp-server ↗

packagehttps://www.npmjs.com/package/fdic-mcp-server ↗