Bancadia MCP

io.github.macphe22由 GitHub 账号 macphe22 发布v2.0.0更新于 Oct 24, 2026

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

已验证Streamable HTTP可网页运行金融商业与电商

概览

AI 生成的概览

通过结构化筛选查询 Bancadia 的美国企业支票账户产品目录,并返回单条产品的完整详情。

可以做什么
  • 按费用、实体类型、州、RTP 通道、集成和 APY 等条件筛选企业支票账户列表,并可针对目标行业或企业画像做软排序
  • 按 slug 获取单条产品的完整详情,包括透支、NSF、休眠等隐性费用,以及功能说明和分档方案明细
适用场景
适合在比较美国企业支票或存款账户选项时使用,希望得到经过筛选和核实的列表及费用、功能细节,而不是泛泛的网络搜索结果。
运行要求
远程 Streamable HTTP 端点,无需本地安装。后续请求需携带 initialize 返回的会话 ID。可在 Authorization 头中提供可选的 bearer token 以将用量计入自己;匿名调用按 IP 限流。
安装前请注意
调用会被记录:每次工具调用都会写入查询事件,每个返回的列表写入匹配事件,返回的 application_url 链接带有归因参数,应原样传递。bearer token 属于凭据,需妥善保管;匿名使用受速率限制。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Bancadia MCP,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.macphe22%2Fbancadia-mcp/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "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.

来源:README.md,提交 5d2de62

工具

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.

输入参数apy_minrtp_networkrtp_supportedinsurance_typemonthly_fee_maxavailable_statesinterest_bearingtarget_industriesentity_types_acceptedfree_transactions_mincash_deposit_availablesub_accounts_supported另有 5 个

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.

输入参数listing_slug必填

版本历史

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

评分

已满足适用检查项的 90%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。