MCP-native banking
Connect Claude Desktop, Cursor, Continue.dev, or any spec-compliant agent to your FinAegis account through one OAuth-protected JSON-RPC endpoint. Move money, exchange, on/off-ramp, send SMS — without writing API glue.
What is MCP?
The Model Context Protocol is Anthropic's open standard for letting AI agents talk to external systems. Instead of every agent vendor rolling its own integration shape, MCP gives them a single wire format — JSON-RPC over HTTP — for discovering tools, calling them, and reading context.
For users, that means an agent you already use (Claude Desktop, Cursor, Continue.dev) can act on your accounts without an extra app or copy-pasted API keys. The agent asks for the scopes it needs, you approve them with a daily spending cap, and it gets a token bound to those limits.
For developers, that means FinAegis works with any spec-compliant client today, and any new client tomorrow — you don't ship new code per agent.
Why FinAegis's MCP is different
Most "MCP-compatible" launches stop at read-only data. Ours moves real money — under proper consent and audit.
Real money rails
Send payments, execute exchanges, on/off-ramp via Stripe Bridge. Not just balance reads — actual settlement, with audit-grade attribution to the token + scope + client.
Spending limits + idempotency
Per-token daily cap (default $500/24h, slider on consent). Atomic Redis lock prevents double-charge on agent retries. The reservation only sticks on success.
Multi-rail payments
Stripe, Tempo, Lightning, Card, x402 — all via the same MCP catalog. The agent picks a rail; the server settles it. SMS sends settle per-message via x402 micropayments.
Regulated foundation
FinAegis is a real banking platform with KYC, AML, and audit trail compliance. Every $-impact agent action is attributed in the regulatory feed — agents inherit the platform's posture, not bolt-on permissioning.
vs. legacy bank APIs
Connecting an agent to a traditional banking REST API is a per-agent, per-bank integration project. MCP collapses that.
| Legacy bank REST | FinAegis MCP | |
|---|---|---|
| Discovery | Per-bank Postman / Swagger; manual. | RFC 9728 + MCP tools/list — automatic. |
| Auth | OAuth flavour per bank, per client type. | OAuth 2.1 + RFC 7591 DCR — agent self-registers. |
| Spending limits | Bolted on per integration, if at all. | Per-token, set on consent screen, server-enforced. |
| Idempotency | Header conventions vary; race-prone. | Required key + atomic SET-NX lock; no double-charge. |
| Audit + AML | Manual mapping of agent → user → tx. | Every call attributed to token + scope + client. |
| New client onboarding | Bank ships new SDK or doc. | Spec-compliant client just connects. |
What agents do with this
Agent treasurer
A finance agent watches accounts and sweeps idle balances into yield, executes FX hedges against the daily cap, and reports back. Spending limit caps the worst case; idempotency keeps retries safe.
Customer-service co-pilot
A support agent reads transaction history, posts reversals up to a per-token cap, and triggers SMS on the user's behalf. Each settlement attributes the action to the support persona for audit.
Recurring agent workflows
Scheduled rebalance, monthly payouts, micro-grants. Refresh-token rollover means a long-lived workflow never has to re-prompt the user — until the user revokes the token.
Ship an agent against FinAegis today
No SDK install, no API key copy-paste. The npm relay handles OAuth and persists your token in the OS keychain.