BankGuard MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@BankGuard MCPShow me the risk summary for all accounts"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
BankGuard MCP
A fraud detection engine that AI assistants can operate directly.
BankGuard is an MCP (Model Context Protocol) server. Connect it to Claude Desktop, Claude Code, or any MCP-capable agent, and the AI gets a set of typed tools for running a banking fraud system: submitting transactions, reading alerts, checking portfolio risk, and freezing or unfreezing accounts. You can literally ask Claude "scan the accounts and freeze anything that looks compromised" and watch it work.
The fraud rules themselves live inside the database as SQLite triggers, so they're enforced no matter who writes - the AI, a script, or a human with a sqlite shell. The AI operates the system; it can't bypass the rules.
Why This Design
Most AI integrations bolt a chatbot onto an app. MCP inverts that: the system exposes a safe operating surface, and any AI client can drive it. This project demonstrates both halves:
The engine - six fraud rules implemented as in-database triggers (invalid amounts, frozen-account blocks, daily limits, velocity detection, risk scoring with auto-freeze, and event emission)
The AI surface - eight MCP tools with docstrings the model reads to decide when and how to act. Destructive actions (freeze/unfreeze) require a reason, which is recorded as an audit alert.
Claude Desktop / Claude Code / any agent
| MCP (stdio)
v
server.py eight typed tools
|
v
bankguard.db SQLite + trigger-enforced fraud rulesRelated MCP server: Fraud Detection MCP
Tools
Tool | What it does |
| All accounts with owner, status, risk score |
| Recent transactions for one account |
| Insert a transaction; fraud rules may reject or flag it |
| Recent alerts raised by the rules |
| Queued events for downstream systems |
| Analyst freeze, reason required and audited |
| Reactivate and reset risk, reason audited |
| Portfolio totals, alerts by rule, riskiest accounts |
Setup
python3 -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
python database.py # creates bankguard.db with 5 seeded accounts
python test_server.py # end-to-end test through a real MCP clientConnect to Claude Code
claude mcp add bankguard -- /path/to/bankguard-mcp/.venv/bin/python /path/to/bankguard-mcp/server.pyConnect to Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"bankguard": {
"command": "/path/to/bankguard-mcp/.venv/bin/python",
"args": ["/path/to/bankguard-mcp/server.py"]
}
}
}Then try prompts like:
"Give me a risk summary of the bank"
"Submit five $100 transactions to account 102 and tell me what happens"
"Which account is riskiest? Show its recent activity and freeze it if warranted"
The Fraud Rules
Amount validation - zero/negative transactions rejected before insert
Status validation - frozen accounts reject all transactions, even direct DB writes
Daily limit - per-day spend cap enforced per account
Velocity detection - 3+ transactions inside 60 seconds raises an alert and +20 risk
Auto-freeze - account freezes itself when risk reaches 60
Event emission - velocity and freeze events queue notifications for downstream consumers
test_server.py proves all six by driving the server over stdio the same way a real client does.
Project Structure
bankguard-mcp/
server.py MCP server - the AI-facing tool surface
database.py SQLite engine with trigger-enforced fraud rules
test_server.py end-to-end test through the MCP protocol
requirements.txtIdeas for Later
Postgres backend for the same tool surface
MCP resources exposing the schema and rule documentation
Human-in-the-loop: mark freeze/unfreeze as requiring client-side approval
Streamable HTTP transport for remote deployment
This server cannot be deployed
Maintenance
Related MCP Connectors
KYC, KYB, AML, wallet screening, transaction monitoring, and fraud workflows for AI agents.
Connect AI agents to financial institution origination, analytics, and compliance workflows.
- BankSyncOAuthio.banksync
Connect AI agents to bank accounts, transactions, balances, and investments.
Read-only finance and operations controls for AI agents with evidence and safe next actions.
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceEnables personal financial management through AI assistants by providing tools to add transactions, check balances, list transaction history, and generate monthly summaries. Supports natural language interaction for tracking income and expenses with categorization.1-
- FlicenseNot gradedqualityDmaintenanceAI-powered fraud detection and investigation platform that exposes tools for querying, scoring, and investigating financial applications using LangGraph, MLflow, and SQLite in-memory.-
- FlicenseAqualityCmaintenanceEnables real-time fraud detection and transaction analysis by integrating with Claude through MCP, providing tools to analyze transactions, flag suspicious activity, and manage fraud rules.9-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to perform banking operations like creating customers and accounts, checking balances, transferring funds, and viewing transaction history through MCP tools.MIT