Fintech · MCP

Banking operations MCP: payment status and alerts, with approval-gated actions

An MCP server for banking operations teams: look up balances, trace payments across ACH, wire, RTP, and FedNow, review open fraud and compliance alerts, and request account holds that require dual approval.

Type: AI agent integration (MCP)
Tools: 5 agent tools
Stack: TypeScript, MCP SDK, Node.js

The problem

"Where is this payment?" is the most common question in banking operations, and answering it means checking several screens. AI assistants could help, but only if access is governed tightly enough for a bank.

The solution

A read-first MCP server over the ledger and payments APIs. Analysts ask in plain language; every answer cites the records it came from, and any action requires maker-checker approval.

Tools the agent can use

account_balanceAvailable, ledger, and pending balancesRead

trace_paymentStatus and timeline of a payment on any railRead

open_alertsOpen fraud and AML alerts for an accountRead

draft_case_noteSummarize an alert's context for the analystWrite

request_holdRequest an account hold; a second user must approveNeeds approval

How it connects

Claude (bank workspace)
MCP Gateway
Banking ops connector
Ledger & payments APIs
Maker-checker approval

Security by design

Account numbers masked unless the role allows full view
Maker-checker approval on every state-changing action
Append-only audit trail attached to the account timeline

Stack

TypeScriptMCP SDKNode.jsPostgreSQLAWS