Bancadia MCP

io.github.macphe22v2.0.0更新於 Oct 6, 2026

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

已驗證Streamable HTTP可網頁執行Business & CommerceFinance

概覽

AI 產生的概覽

讓助理以結構化篩選條件查詢 Bancadia 的美國企業支票帳戶產品目錄。

功能
透過遠端 Streamable HTTP 端點提供兩個工具：query_business_checking 可依費用、實體類型、州、RTP 通道、整合與 APY 等條件篩選企業支票帳戶清單；get_business_checking_listing 可依 listing_slug 回傳單一清單的完整詳情，包含費用、功能以及各方案層級的細分。工作階段以 initialize 建立，工具以 tools/list 列舉，呼叫則透過 tools/call 完成。
適用情境
適合助理需要比較或查詢美國企業支票帳戶產品的情境，例如回答帳戶費用、依實體類型或州的資格要求，以及可用整合與利率資訊等問題。
執行需求
需要支援 Streamable HTTP 的遠端 MCP 用戶端。後續請求必須帶上 initialize 回傳的工作階段 ID。呼叫工具需要從 Bancadia 開發者入口取得的 Authorization bearer 權杖；initialize 與 tools/list 不需要。設有依權杖的速率限制。
安裝前請注意
Authorization bearer 權杖屬於憑證，應妥善保密，並在 tools/call 時以請求標頭送出。所述工具為唯讀，但查詢內容與權杖會傳送至第三方服務，且依權杖的速率限制可能回傳 429 回應。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Bancadia MCP，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "bancadia-mcp": {
      "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 also needs a 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 and Authorization: Bearer <token> required. Per-token sliding-window rate limiting applies (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, obtain a bearer token 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.

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.

來源：README.md，提交 9db6807

工具

0
工具後設資料尚未被收錄。

版本歷史

1
  1. v2.0.0最新Sep 16, 2026