Banking and fintech represent some of the highest-stakes use cases for MCP — AI agents that can query account balances, enrich transactions, assess credit risk, and navigate payment APIs must do so with rigorous security and compliance. The ecosystem has moved faster than expected: major players like Plaid, Adyen, Square, Marqeta, and Morningstar all ship official MCP servers. Part of our Finance & Business MCP category.

This review covers open banking and account aggregation (Plaid, TrueLayer, multi-provider), payment processing (Adyen, Square, Ramp), banking-as-a-service (Marqeta), financial market data (Morningstar, Bloomberg, EODHD, Financial Datasets), neobank and challenger bank integrations (Revolut, Mercury), lending and credit (LoanPro, Carrington Labs), KYC/AML (iDenfy, Kyonis), and transaction enrichment (Ntropy). For cryptocurrency and DeFi, see our Cryptocurrency & DeFi MCP Servers review. For payment-specific servers like Stripe and PayPal, see our dedicated Stripe MCP Server and PayPal MCP Server reviews.

The headline finding: read-only design dominates — most financial MCP servers deliberately exclude write operations to minimize risk. Plaid leads open banking with an official remote MCP server and multiple community implementations. Payment processors are all-in with Adyen, Square, and Marqeta shipping official servers. Financial data is well-covered by Morningstar (200K+ securities) and community Bloomberg access. Core banking is completely absent — no servers from Thought Machine, Mambu, Temenos, FIS, or Fiserv. Security patterns are maturing with OAuth 2.1, encrypted token storage, PII exclusion, and stdio-only transport gaining traction.

Open Banking & Account Aggregation

Open banking MCP servers connect AI agents to bank accounts, transactions, and balances through regulated APIs. This is the most active sub-category, with both official and community implementations.

Plaid Ecosystem

ServerStarsLanguageLicenseToolsOfficial
Plaid Dashboard MCPRemotePythonMITDashboard + sandboxYes
PlaidMCP (arjabbar)C# / .NET8+ toolsNo
bank-mcp (elcukro)TypeScript3 tools, 4 providersNo
304techmaven/plaid-mcpTypeScriptAuth + transactionsNo

Plaid’s official MCP is a remote server at api.dashboard.plaid.com/mcp using Streamable HTTP transport. It provides integration health monitoring, API usage metrics, Link conversion rate optimization, and support diagnostics — focused on the developer dashboard rather than end-user banking data. The companion plaid/ai-coding-toolkit (MIT, Python) provides sandbox tools like get_mock_data_prompt, search_documentation, and get_sandbox_access_token. Published on PyPI as mcp-server-plaid. Authentication uses OAuth Bearer tokens via Plaid Dashboard authorization, preserving all existing security standards.

PlaidMCP (arjabbar, C# / .NET) is the standout community implementation. It offers AES-GCM 256-bit encrypted token storage at rest, uses secure item_ref aliases instead of raw access tokens, and provides configurable ephemeral or persistent storage. Tools include Link token creation, public token exchange, account listing, balance retrieval, and transaction sync with cursor-based pagination.

bank-mcp (elcukro, TypeScript) is a multi-provider aggregator supporting Plaid, Teller, Enable Banking, and Tink — covering 15,000+ institutions across the US and Europe. Deliberately read-only with only listAccounts, listTransactions, and getBalance. Runs as a stdio process with no HTTP server, no open port, and no network attack surface. Only 4 runtime dependencies. Credentials are never logged, and no data leaves the local machine. Plaid provides 104 sub-categories with confidence scores; Tink covers 3,400+ European banks; Enable Banking uses PSD2; Teller uses mTLS with a free tier of 100 live connections.

TrueLayer (Experimental)

TrueLayer has experimental MCP integration documented at docs.truelayer.com but explicitly states it is NOT officially supported or maintained. Tools include get_accounts, get_transactions, and notably create-truelayer-payout — one of the few banking MCP servers with a write operation that initiates real payments. This carries significant security implications. Community implementation at tkom04/openbankingmcp.

BANKSapi (Commercial, PSD2-Licensed)

BANKSapi (banksapi.de) is a German fintech offering a commercial MCP server with PSD2 AIS and PIS licensing from BaFin. Covers 3,000+ providers (99% of German bank accounts, credit cards, custody accounts, loans). ISO 27001 certified, GDPR-compliant, hosted in high-security German data centers. Model-agnostic — works with local or hosted LLMs. Not open source.

E2E MCP Gateway (Middle East)

E2E MCP (e2emcp.com) provides a federated gateway for UAE, KSA, and Bahrain, compliant with CBUAE Open Finance framework. Manages compliance, encryption, and local data residency. Does not require users to be licensed payment providers.

openbanking-mcp (Demo)

openbanking-mcp (collinsrj, TypeScript) is an educational demo showing how Open Banking account and transaction data can be exposed via MCP resources using RFC 6570 URI Templates.

Payment Processing

Payment MCP servers let AI agents interact with checkout, order management, and merchant services APIs.

ServerStarsLanguageLicenseToolsOfficial
Adyen MCP~47TypeScriptMITCheckout + Management + webhooksYes (alpha)
Square MCP~95TypeScriptFull API ecosystemYes
Ramp MCPRemoteExpense + cards + approvalsYes

Adyen (adyen/adyen-mcp, 47 stars, MIT, TypeScript) is in alpha but already functional. Covers Checkout API and Management API with tools for webhook configuration, merchant management, and onboarding links. Available on npm as @adyen/mcp. Key feature: natural language to API call translation (e.g., “Refund order #12345”).

Square (square/square-mcp-server, 95 stars, TypeScript) provides the full Square API ecosystem — payments, orders, inventory, and customer management. Auto-generated from OpenAPI specs. Supports remote MCP with OAuth (recommended) or local with ACCESS_TOKEN. Block has been integrating MCP across its fintech stack.

Ramp (mcp.ramp.com, hosted) is an official MCP server for corporate expense management. Tools cover expense completion (memos, receipts, categories, trips), card management (lock/unlock, activate, generate agent card credentials), spend analysis, transaction auditing, and approval management. Every write is recorded in Ramp’s Audit Log, and access respects each user’s role permissions.

Banking-as-a-Service

Marqeta

Marqeta (marqeta/marqeta-mcp) ships an official MCP server with 33 tools across 7 service categories: issue virtual cards, set spend/velocity controls, create and submit disputes, retrieve transaction details, and flag anomalies. Generated from OpenAPI specifications. This is one of the highest-risk financial MCP servers — it can issue cards and manage disputes on live financial infrastructure. Authentication via environment variables (MARQETA_API_URL, MARQETA_USERNAME, MARQETA_PASSWORD, MARQETA_PROGRAM_SHORT_CODE).

A companion community server, marqeta-diva-mcp (zvika-finally), focuses on data insights, visualization, and analytics.

Financial Market Data

Financial data MCP servers provide stock prices, ratings, research, and analytics to AI agents.

ServerStarsLanguageCoverageToolsOfficial
Morningstar MCP~19Python200K+ securities2 mainYes
blpapi-mcpBloomberg Terminal18 toolsNo
EODHD MCPGlobal markets77 toolsSemi-official
Financial DatasetsPythonUS stocks5 categoriesYes
FinanceKit MCPStocks + crypto17 toolsNo

Morningstar (Morningstar/morningstar-mcp-server, 19 stars, MIT, Python) provides two main tools: Datapoint (market cap, ratings, fair value, closing price, total return, economic moat, EPS, NAV, fund size, sector, domicile) and Articles (editorial content, methodologies, thematic research, investment strategies). Covers 200,000+ global securities. Integrated with Claude, ChatGPT, Copilot Studio, and Microsoft Foundry. Requires a licensed Morningstar account. Note: the GitHub repo is archived — development has moved to Morningstar’s internal hosting.

blpapi-mcp (djsamseng, community) wraps the Bloomberg Terminal API with 18 financial data tools covering market data, bulk data, technical analysis, screening, and calendars. Requires a running Bloomberg Terminal (BBComm accessible). Bloomberg has committed to MCP internally but has not released a public official server. Integrates with Cursor, Claude Code, and Aider.

EODHD provides 77 read-only tools, 100+ documentation resources, and 3 prompt templates (analyze_stock, compare_stocks, market_overview). Community implementations at Enlavan/EODHD_MCP_server and tradermonty/eodhd-mcp-server. V2 supports OAuth authentication.

Financial Datasets (financial-datasets/mcp-server, Python) covers stock prices (OHLCV), income statements, balance sheets, cash flow statements, and stock screening with metric/ratio filters. Uses OAuth 2.1 — no API key needed for interactive clients like Claude.

FinanceKit MCP (vdalhambra, community) offers 17 tools including stock quotes, technical analysis (RSI, MACD, Bollinger Bands, ADX, Stochastic, ATR, OBV), crypto data via CoinGecko, risk metrics, options chains, earnings calendar, and portfolio analysis. No API keys required for stocks and crypto — technical indicators calculated locally.

FinMCP (Finance-LLMs, MIT) provides a deep research engine with multi-market integration (Indian NSE/BSE + global via Yahoo Finance), trading platform integration (Upstox), and specialized financial document analysis. Multi-provider AI support via NVIDIA, OpenAI, and Fireworks AI.

Neobank & Challenger Bank Integrations

ServerLanguageFocusOfficial
Revolut X TradingTrading data, 11 toolsYes
revolut-mcp (jeff-nasseri)Personal bankingNo
Mercury banking (multiple)Python/TSBusiness bankingNo
mono-mcp (sin4ch)Nigerian banking, 12 toolsNo

Revolut X (revolut-engineering/revolut-x-api) is an official MCP server from Revolut Engineering with 11 tool files covering market data, account management, orders, monitoring, and grid strategy backtests. Read-only by design — cannot place, modify, or cancel orders. In beta. Notable: two engineers reportedly built a working trading system in 30 minutes using this server.

Mercury has three community-built MCP servers: jbdamask/mcp-mercury-banking (Python, read-only, tested with Claude Desktop), dragonkhoi/mercury-mcp (lightweight API bridge), and klodr/mercury-invoicing-mcp (adds full Invoicing API support including recurring invoices). None are official Mercury products.

Mono Banking MCP (sin4ch/mono-mcp) provides 12 tools plus webhook support for Nigerian banking operations via the Mono Open Banking API. Uses FastMCP with async httpx and SQLAlchemy webhook storage.

No MCP servers found from Chime, N26, Monzo, or Starling.

Lending & Credit

ServerLanguageFocusOfficial
LoanPro MCPGoLoan servicingYes
Carrington LabsCredit risk scoringYes (commercial)

LoanPro (MiloCreditPlatform/loanpro-mcp-server, Go) is an official server with modular packages for loan operations, customer operations, and payment operations. Supports HTTP, SSE, and stdio transports. Read-only access to financial data with compliance guardrails enforced programmatically and full audit trail for both human and AI agent actions. Positioning: “Onboard a new servicing employee instantly.”

Carrington Labs (carringtonlabs.com/mcp-server, commercial) provides deterministic credit risk assessments — not probabilistic — with Cashflow Score, Credit Risk Model outputs, and explainability. Returns only a unique record ID and model outputs, never personally identifiable information. Score plus key factor explanations meet Equal Credit Opportunity Act requirements. Announced November 2025, broader availability expected.

KYC & AML

ServerFocusOfficial
iDenfy MCPDocumentation access (KYC/KYB/AML)Yes
Kyonis ComplianceKYC verification + AML screeningYes
SardineFraud detection AI assistantYes (internal)

iDenfy (documentation.idenfy.com/resources/mcp, launched April 2026) is a documentation-access MCP server — it searches iDenfy’s live docs and returns API field names, endpoints, and working code examples. It cannot trigger verification flows, access live data, dashboard, sessions, API keys, or customer data. Free for all developers. Covers KYC, KYB, and AML products.

Kyonis Compliance (listed on PulseMCP) provides KYC verification, AML sanctions screening, and due diligence checks via the Kyonis API.

Sardine (sardine.ai) uses MCP internally for a fraud detection AI assistant covering device intelligence, behavior biometrics, and ML fraud detection across onboarding, login, and payments with real-time transaction interdiction in hundreds of milliseconds. Not publicly available as a standalone MCP server.

Transaction Enrichment

Ntropy (ntropy-network/ntropy-mcp, MIT) enriches raw transaction data with 95%+ merchant identification and categorization on both business and consumer data. Tools include check_connection, transaction enrichment (with parameters for description, date, amount, entry type, currency, country), and account holder management. Requires an external Ntropy API key.

Security Patterns Across Financial MCP Servers

Financial MCP servers have developed distinct security patterns worth noting:

  • Read-only by default: bank-mcp, Revolut X, Mercury, LoanPro, and most data servers deliberately exclude write operations. The few servers with write access (TrueLayer payouts, Marqeta card issuance, Ramp expense management) carry elevated risk profiles.
  • PII exclusion: Carrington Labs returns only record IDs and model outputs, never personally identifiable information. This pattern should be standard for credit and lending MCP servers.
  • Encrypted token storage: PlaidMCP uses AES-GCM 256-bit encryption at rest with alias-based token references.
  • OAuth 2.0/2.1: Becoming the standard authentication method for remote financial MCP servers (Plaid, Square, Financial Datasets, EODHD v2).
  • Stdio-only transport: bank-mcp and others prefer stdio to eliminate network attack surface entirely.
  • Audit logging: Ramp and LoanPro record every AI agent action in audit trails.
  • Sandbox-first development: Plaid, TrueLayer, and Revolut mandate sandbox environments before production access.

What’s Missing

  • Core banking vendors: No MCP servers from Thought Machine, Mambu, Temenos, FIS, or Fiserv. These vendors serve the world’s largest banks but have not adopted MCP.
  • Major neobanks: Beyond Revolut, no MCP servers from Chime, N26, Monzo, Starling, or SoFi.
  • Full Bloomberg access: The community blpapi-mcp wrapper requires a Bloomberg Terminal license. No public Bloomberg MCP server exists.
  • LSEG/Refinitiv: Has partnered with Microsoft and Anthropic for managed MCP access but offers no self-hostable public server.
  • PSD3-specific servers: PSD3 is still in legislative process; no MCP servers target it yet.
  • Crypto banking: While we cover crypto in our Cryptocurrency & DeFi review, there are no MCP servers bridging traditional banking with stablecoin or CBDC operations.
  • Dedicated fraud prevention: Sardine’s MCP is internal-only. No public MCP servers for Featurespace, Feedzai, or other fraud platforms.

Rating: 3.5 / 5

The banking and fintech MCP ecosystem is stronger than expected for a highly regulated industry. Official servers from Plaid, Adyen, Square, Marqeta, Morningstar, Ramp, and LoanPro demonstrate genuine institutional commitment to MCP adoption. The community has filled important gaps with multi-provider aggregators like bank-mcp and Bloomberg Terminal wrappers. Security patterns are maturing appropriately — read-only defaults, PII exclusion, encrypted storage, and audit logging reflect the seriousness of financial data handling.

However, the complete absence of core banking vendors is a significant gap. Thought Machine, Mambu, Temenos, FIS, and Fiserv serve the backbone of global banking but offer no MCP integration. Major neobanks beyond Revolut are also missing. The rating reflects strong coverage in payments and market data but weak representation from the institutions that actually hold deposits and process the majority of financial transactions.