NorthPark Banking API
Server Details
Demo banking MCP server: accounts, transactions and payments. OAuth 2.1 with DPoP.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 6 tools
Each tool targets a clearly distinct resource and action: adding vs listing payees, listing accounts vs transactions, exporting statements, and making payments. The only potential overlap—add_payee and make_payment—is resolved by the descriptions, since one creates a payee and the other pays an existing payee or wallet.
All six tools follow a consistent snake_case verb_noun pattern: add_payee, export_statements, list_accounts, list_payees, list_transactions, make_payment. The convention is predictable and readable throughout.
Six tools is well within the typical 3–15 range and each tool earns its place by covering a distinct banking operation. The surface is compact without feeling arbitrarily thin.
Core read and payment workflows are present, but payee management is incomplete (no update or delete payee) and there is no explicit transfer-between-own-accounts or payment status/cancellation operation. These are notable gaps for a banking API, though agents can partially work around them via transactions and statements.
Available Tools
6 toolsadd_payeeCInspect
Add a NorthPark or external US payee
Inputs: otp (required), bank (required), name (required), account_id (required), +1 more.
export_statementsCInspect
Export full statements for all accounts as CSV, including counterparties.
Inputs: account_id.
list_accountsBInspect
List your accounts and balances
Inputs: no named parameters.
list_payeesCInspect
List your payees
Inputs: no named parameters.
list_transactionsCInspect
Recent transactions on one of your accounts
Inputs: account_id (required), limit.
make_paymentCInspect
Pay an existing payee or an external wallet address. Large payments settle instantly.
Inputs: amount (required), payee_id (required), from_account_id (required), idempotency_key (required), +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
MCP server for Modern Treasury — payment orders, transactions, counterparties and ledgers.
MCP server for verifying EUDI/Talao wallet data via OIDC4VP (pull) for AI agents.
MCP server for Codat — companies, connections, invoices, bills and financial statements.
MCP server for mandates, delegation, policy-gated execution, credential grants, and audit.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA proof-of-concept MCP server implementing OAuth 2.1 authorization with CIMD client registration and PKCE, demonstrating protected resource access and step-up authentication.-
- FlicenseNot gradedqualityDmaintenanceA production-grade MCP server for a fictional digital bank, exposing tools for an AI copilot to service customers across the full risk spectrum from read-only lookups to money movement and destructive admin actions, with OAuth 2.1 security and a realistic dataset.23 npm1-
- AlicenseNot gradedqualityDmaintenanceA demo MCP server protected by OAuth (DCR), enabling hands-on exploration of OAuth flow for local MCP servers.MIT
- FlicenseNot gradedqualityBmaintenanceRemote MCP server for Deutsche Bank BizBank/SME API, enabling secure OAuth with PKCE and tools for account and transaction management.-
Glama MCP Gateway
Add one secure layer between your agents and this server.