Bancadia MCP

io.github.macphe22Published by GitHub account macphe22v2.0.0Updated Oct 24, 2026

Query Bancadia's registry of US business checking account products with structured filters.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Queries Bancadia's registry of US business checking account products with structured filters and returns full listing detail.

What you can do
  • Search business checking listings by fees, entity types, states, RTP rails, integrations and APY, optionally soft-ranking toward a target industry or business profile
  • Retrieve full detail for one listing by slug, including gotcha fees such as overdraft, NSF and dormancy, plus feature narratives and per-plan-tier breakdowns
When to use it
Useful when comparing US business checking or deposit account options and you want filtered, verified listings with fee and feature detail rather than general web results.
Requirements
Remote Streamable HTTP endpoint; no local install. A session ID from initialize must be sent on later requests. An optional bearer token in the Authorization header credits usage to you; anonymous calls are rate limited per IP.
Before you install
Calls are logged: every tool call writes a query event and each returned listing a match event, and returned application_url links carry attribution parameters that should be passed through unmodified. A bearer token is a credential and should be kept secret; anonymous use is rate limited.

Installation

In SourceWeft

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

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.macphe22%2Fbancadia-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "bancadia": {
      "type": "http",
      "url": "https://mcp.bancadia.com/"
    }
  }
}

README

Bancadia MCP

A Model Context Protocol server that lets MCP clients (Claude, other LLM agents, etc.) query Bancadia's registry of business deposit account products (US only) — with structured filters.

Runs as a Cloudflare Worker on Hono, exposing MCP over JSON-RPC 2.0 (Streamable HTTP transport), backed by Supabase (Postgres) with an Upstash Redis caching/rate-limiting layer.

Endpoints

MethodPathPurposeAuth
GET/healthLiveness checknone
GET/.well-known/mcpPublic discovery/manifest (server info + tool list)none
POST/JSON-RPC 2.0 endpoint — initialize, tools/list, tools/callsession; tools/call accepts an optional bearer token
GET/Standalone SSE stream (server-initiated messages, keep-alive)session
DELETE/Terminate a sessionsession

MCP session lifecycle

  1. POST / with method: "initialize" — no auth required. Returns an Mcp-Session-Id response header; every subsequent request must send that value back as the Mcp-Session-Id request header.
  2. POST / with method: "tools/list" — session required, no bearer token needed. Returns the tool manifest.
  3. POST / with method: "tools/call" — session required; Authorization: Bearer <token> is optional (no header = anonymous, rate limited per IP; an invalid token is a 401). Sliding-window rate limiting applies (per token, or per IP via ANON_RATE_LIMIT_REQUESTS / ANON_RATE_LIMIT_WINDOW_SECONDS, default 60 / 60s) (X-RateLimit-* response headers on both success and 429).

Responses are plain JSON by default, or Server-Sent Events if the request's Accept header includes text/event-stream.

For production use, optionally obtain a bearer token (credits usage to you) from the Bancadia developer portal — see bancadia.com/docs for full API documentation.

Available tools

ToolPurpose
query_business_checkingFilter business checking listings (fees, entity types, states, RTP rails, integrations, APY, etc.)
get_business_checking_listingFull detail on one listing by listing_slug — fees and features, including per-plan-tier breakdowns

See src/lib/tools.ts for the full JSON Schema of each tool's arguments, or query GET /.well-known/mcp / tools/list directly.

Profiles (legacy and v2)

The MCP tool set is chosen per session. The default is MCP_PROFILE (wrangler.toml, currently v2); a client opts into the old two-tool set at initialize with the header X-Bancadia-Profile: legacy or the URL query ?profile=legacy (header wins; read once, stored on the session). A tool name outside the session's profile is -32601 Unknown tool.

ProfileTools
legacyquery_business_checking, get_business_checking_listing (unchanged)
v2list_business_checking, search_facts, fees_by_type, get_listing — slim, paged JSON backed by Postgres functions; schema in docs/v2-tool-manifest.json, behavior in docs/v2-tool-spec.md

v2 lists accept the usual filters plus has_active_promotion (true: only listings with a current promotion, rows include it; recorded for only some banks) plus remote_deposit_capture, check_writing_available, multicurrency_support, bill_pay_available, virtual_cards_available, corporate_card_available, physical_debit_card_available (booleans) and min_insured_usd (banks with extended coverage but no published amount come back in possible_matches, with an application_url). Fields named in fields always appear (false = not offered, null = not published); apy_max_condition and outgoing_domestic_wire_fee_note qualify their value automatically. get_listing takes query (only matching features; features are capped, see features_shown/features_truncated), fees_by_type takes 1-5 fee types (fees_omitted when capped) and search_facts retries a zero-hit multi-term query as any-term (relaxed: true). Lists default to 7 rows (max 20, clamped; next_offset pages). DB validation errors (SQLSTATE 22023) are returned as -32602 with the valid values. npm run measure:tokens prints the v2 schema and default-list token sizes for a running Worker.

REST API (always v2)

Resource-oriented routes, all with { data, meta } envelopes: GET /v1/business-checking-listings (list; data is an array of rows, default 7 / max 20, paging in meta), /business-checking-listings/{listing_slug}[?sections=], /business-checking-listings/{listing_slug}/fees|features|promotions|plans (no query params; meta.listing carries the tracked link), and the cross-listing reads /business-checking-listings/-/fees and /-/facts (use - in place of {listing_slug} to read across all listings). GET /v1/business-checking and /v1/business-checking/{listing_slug} remain as deprecated aliases (Deprecation: true and a successor-version Link header). REST ignores MCP_PROFILE. This is a breaking change from the earlier REST list (which returned every listing with full detail). OpenAPI: GET /v1/openapi.json, checked in as docs/openapi-rest.json (regenerate with npx tsx scripts/print-openapi.ts > docs/openapi-rest.json; a test fails on drift).

application_url attribution tags

Every application_url returned by tools/call is an absolute https://bancadia.com/go/... link with attribution params appended: src=mcp (src=rest on the REST API) and qr=<request_id>, where request_id is a UUID generated once per tools/call and also written as that call's query_events.request_id and on each of its query_match_events rows (so a /go click can be joined back to the tool call, and listing, that surfaced it). Params already present on the stored URL are never overwritten. Every call to a known tool gets a query_events row — including zero-result calls, calls rejected for invalid arguments (status = 'invalid_args') and failed calls (status = 'error') — while query_match_events holds one row per returned listing. Host-prefixing and tagging happen in one layer: applyApplicationUrlHost (src/lib/urls.ts) for legacy tools, tagResponse (src/lib/tag-response.ts, with a runtime assert that every bank row is tagged) for v2, both applied in runTool.

Clients and agents should pass application_url through unmodified, including its query string. Stripping the params loses attribution for that click.

Getting started

bash
npm installcp .dev.vars.example .dev.vars   # fill in Supabase + Upstash credentialsnpm run dev                      # wrangler dev — local server

wrangler.toml [vars] provides non-secret defaults (test Supabase/Upstash URLs, session TTL, allowed origins) shared by both npm run dev and the test suite; real secrets go in .dev.vars (git-ignored).

Commands

bash
npm run dev               # wrangler dev — local servernpm test                  # vitest run (runs inside workerd via @cloudflare/vitest-pool-workers)npm run lint              # tsc --noEmitnpm run deploy:staging    # wrangler deploy --env stagingnpm run deploy:production # wrangler deploy --env production

Run a single test file:

bash
npx vitest run src/__tests__/query-business-checking.test.ts

Environments

  • staging — bancadia-mcp-staging, workers.dev enabled. Deployed automatically by CI on every push/PR to main.
  • production — bancadia-mcp-production, routed at mcp.bancadia.com/*. Deployed manually via npm run deploy:production.

Secrets for each environment are set with wrangler secret put <KEY> --env <environment> and are never committed.

Architecture

See CLAUDE.md for a detailed guide to the codebase: request flow, auth/session/rate-limit design, and the Supabase hybrid schema (base tables + per-product-type details tables) that the query handlers are built around.

Source: README.md at commit 5d2de62

Tools

2

query_business_checking

Query the Bancadia registry for business checking account products using compound filter criteria. Returns active, verified listings from financial institutions. Optionally accepts target_industries/target_business_profiles to soft-rank results toward listings built for a given business type or stage — non-matching but eligible listings are still returned, just ranked lower. Each result's application_url is a tracked Bancadia link: give it to the user exactly as returned, including its query string.

Parametersapy_minrtp_networkrtp_supportedinsurance_typemonthly_fee_maxavailable_statesinterest_bearingtarget_industriesentity_types_acceptedfree_transactions_mincash_deposit_availablesub_accounts_supported+5 more

get_business_checking_listing

Get full detail on one specific business checking listing, including gotcha fees (business_deposit_fees, e.g. overdraft, NSF, dormancy) and feature narrative (business_deposit_account_features) not returned by query_business_checking's broad list results. Fees/features that apply to only one plan tier (e.g. a Standard/Plus/Premier ladder) are nested under that tier in plan_tiers[].fees / plan_tiers[].features; tier-agnostic ones are in the top-level general_fees / general_features. Use this as a follow-up after query_business_checking to dig deeper on one listing the caller already identified by its listing_slug. Each result's application_url is a tracked Bancadia link: give it to the user exactly as returned, including its query string.

Parameterslisting_slugrequired

Version history

1
  1. v2.0.0LatestSep 16, 2026

Score

90% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.