Try it without a bank
Two invented accounts in EUR and GBP. A real MCP client/server demo, without a token, consent flow or cloud service.
Local · Read-only · Experimental
Explore accounts and transactions through MCP, without connecting a bank. Exact decimal amounts, explainable summaries and a demo built from invented data.
{
"source": "synthetic-fixtures",
"live": false,
"as_of": "2026-01-05",
"data": {
"amount": "1234.56",
"currency": "EUR"
}
}Illustration, shortened response. Invented money.
The date is fixed fixture metadata, not freshness.
Built for understanding
Start with a reproducible local session and inspect what the tools return. Every result says where it came from and what it cannot establish.
Two invented accounts in EUR and GBP. A real MCP client/server demo, without a token, consent flow or cloud service.
Decimal strings instead of float money. Separate currencies and booked/pending rows. No inferred exchange conversion.
Bounded inputs, synthetic negative tests and independent review. A green test is not proof of live compatibility or complete history.
The connected surface
All five operate on embedded fixtures. They do not call a bank, write financial state or activate the isolated provider experiments.
| Tool | Purpose |
|---|---|
list_accounts | List two fictional accounts, without balances. |
get_balance | Read an invented decimal balance and currency. |
get_transactions | Page through bounded date ranges of synthetic movements. |
search_transactions | Find literal description matches within selected fixtures. |
summarize_transactions | Separate inflow, outflow and net by currency and status. |
Transaction dates are inclusive, with at most 366 days per range. A completed page is not evidence of a complete real bank history. See the README for arguments and limits.
Quick start
Python 3.10 or newer and pip. Clone the repository, create a virtual environment and run the demo from the project root.
On Windows, use py -3 -m venv .venv and run .venv\Scripts\python.exe directly if activation is restricted. No execution-policy changes are required.
git clone https://github.com/HALCONDEORO/personal-banking-mcp.git cd personal-banking-mcp python3 -m venv .venv . .venv/bin/activate python -m pip install -r requirements.txt python -m pip check python -m unittest -q python test_server.py --demo
Local execution does not make your AI client offline. It may send returned data to an AI service. Check its privacy settings.
What stays outside
Separate experiments
Normalization, pagination, consent design and request budgets are tested with synthetic transports. Export and recurring-charge candidates are pure library functions, not extra connected MCP tools.
A recurring pattern is not a confirmed subscription or predicted debit. Never put real statements, credentials, keys or session tokens into the repository, issues, logs or screenshots.
Read the implementation boundaries ↗The finished-product goal
The destination is a personal banking MCP that reads authorized accounts through Enable Banking, keeps the signing key on the owner's computer and makes accounts, balances and transactions useful without moving money.
Reviewed registration, an accepted redirect and account-owner SCA. Published Revolut coverage is not proof that a particular account works.
Verified Windows key custody, permissions, safe transport, private storage, revocation and cleanup. These are release gates, not completed features.
Exact read-only data, clear provenance and explainable search, summaries and patterns. No fabricated completeness, subscriptions or fraud claims.
Current status: synthetic MCP only. No live bank has been connected through this project workflow. No delivery date, production-readiness claim or account-specific compatibility promise.
Full goals and release gates ↗Go further
Install details, provider limits and contribution rules live with the code. Changes go through a focused pull request, independent review and checks at the exact head.