The MCP server for personal finance, written in Rust
The MCP server for personal finance, written in Rust
active Production-safe Score 92/100 http no auth
At a glance
| Endpoint | https://app.driggsby.com/mcp |
|---|---|
| Source | https://github.com/driggsby/driggsby |
| Transport | http |
| Tools | 33 |
| Auth | none |
| First seen | 2026-08-22 00:11:30 |
| Last checked | 2026-11-17 21:52:32 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 616 / 917 ms |
| Last successful check | 2026-11-17 21:52:32 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (33)
archive_custom_asset_or_liability— Archive one existing custom asset or liability by reference. First call `list_assets_and_liabilities`, find the one custom row the user meancreate_custom_asset_or_liability— Create a new custom asset or liability that should count toward the user's net worth. Use this directly for requests like 'add my boat worthdelete_automation— Delete an automation: it stops running and leaves the user's list. Confirm with the user first; there is no undo. If a check is in progressdelete_transaction_items— Remove the saved items from the user's card charges, for a charge that was matched to the wrong order or that the user wants to start over.delete_transaction_rule— Deletes one transaction rule by rule_ref. Its category effects and tag assignments go with it: each row then follows another of the user's remail_me— Send a Driggsby-rendered email to the authenticated account owner's verified address. No recipient fields, CC/BCC, attachments, HTML/CSS, orexport_cash_transactions— Create a downloadable CSV file of cash transactions for a required date window, then return a short-lived Driggsby download URL. The downloaget_automation_run— Status and outcome of one automation run: `run_status` (queued, running, finished), the finished run's `outcome` (alerted, nothing_to_reportget_history— Show how the user's linked-account balances, investment holdings, liabilities, or user-managed custom items changed over time. Choose one higet_other_cash_flow_out— The Spending page's "Other cash flow out" for one week (Monday to Sunday), calendar month or calendar year: money that left the user's linkeget_overview— Summarize the user's overall financial state in an agent-first format. The response includes explicit rollups, a balance breakdown, linked aget_skill— Load one of Driggsby's skills: its full instructions, verbatim, for you to follow from start to finish. Skills: `cost` cuts what the user paget_watch_activity— Watches are coming soon to Driggsby: rules that tell the user the moment something happens in their accounts. They aren't available yet, solist_accounts— List the user's active linked accounts with stable opaque refs and account balance context. get_overview summary_rollups contains the balanclist_assets_and_liabilities— List the user's assets and liabilities in one normalized balance-sheet view. This includes linked-account positions and user-managed customlist_automations— Driggsby automations run on Driggsby's servers against the user's linked accounts, on a schedule, without the user or this conversation beinlist_investment_holdings— List the user's current investment positions. Each row includes `account_name`, `institution_name`, `account_type`, and `account_subtype`. Ulist_outstanding_debts— List linked debts with positive current_balance values, along with consumer-readable balances, payment fields, due dates, `account_type`, anlist_recurring_transactions— List the user's recurring bills and income, with usual amounts and predicted next dates. Each row includes `account_name`, `institution_namelist_transaction_rules— Every transaction rule in the user's workspace, one line per rule (pass rule_ref when only one is needed): its rule_ref, name, `contract` (wlist_transaction_tags— The workspace's tag vocabulary: every tag's slug, label, one-sentence description, and how many transactions and rules carry it. Call this Bpreview_transaction_rule— To change a transaction's category — one transaction, or every one like it — make a transaction rule; there is no separate category tool. Apreview_watch— Watches are coming soon to Driggsby: rules that tell the user the moment something happens in their accounts. They aren't available yet, soquery_cash_sql— Read-only SQL for cash spending and income questions the dedicated tools don't answer. Use `search_cash_transactions` first when it fits. Squery_investment_sql— Read-only analytical escape hatch for investment-history questions that do not map cleanly to the dedicated tools. Use `search_investment_acquery_item_sql— Read-only analytical SQL over the items behind the user's itemized charges: one row per item an agent saved with `save_transaction_items`, wrun_automation_now— Start one check of an automation right now, outside its schedule, on the automation's current `model`. Returns instantly with the queued (orsave_automation— Driggsby automations run on Driggsby's servers against the user's linked accounts, on a schedule, without the user or this conversation beinsave_transaction_items— Save the items behind the user's card charges: what an Amazon (or any store's) order actually bought, or what was on a receipt the user gavesave_transaction_rule— Creates a transaction rule, or changes one by rule_ref, and applies it to the matching history at once; returns the applied count and the tosearch_cash_transactions— Search depository and credit-account transaction history by text, merchant, date range, amount, account, best-available Driggsby category, ssearch_investment_activity— Search investment history and portfolio events using Plaid investment transaction type and subtype semantics. Results include `account_name`update_custom_asset_or_liability— Update one existing custom asset or liability by reference. First call `list_assets_and_liabilities`, find the one custom row the user means
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:52:32 | ✓ | ✓ | 785 ms | 90 | active |
| 2026-11-17 21:37:31 | ✓ | ✓ | 885 ms | 90 | active |
| 2026-11-17 21:22:30 | ✓ | ✓ | 846 ms | 90 | active |
| 2026-11-17 21:07:29 | ✓ | ✓ | 830 ms | 90 | active |
| 2026-11-17 20:52:28 | ✓ | ✓ | 611 ms | 90 | active |
| 2026-11-17 20:37:27 | ✓ | ✓ | 714 ms | 90 | active |
| 2026-11-17 20:22:19 | ✓ | ✓ | 652 ms | 90 | active |
| 2026-11-17 20:07:13 | ✓ | ✓ | 604 ms | 90 | active |
| 2026-11-17 19:51:28 | ✓ | ✓ | 574 ms | 90 | active |
| 2026-11-17 19:36:22 | ✓ | ✓ | 637 ms | 90 | active |
| 2026-11-17 19:21:09 | ✓ | ✓ | 607 ms | 90 | active |
| 2026-11-17 19:05:56 | ✓ | ✓ | 759 ms | 90 | active |
| 2026-11-17 18:50:43 | ✓ | ✓ | 608 ms | 90 | active |
| 2026-11-17 18:35:33 | ✓ | ✓ | 737 ms | 90 | active |
| 2026-11-17 18:20:32 | ✓ | ✓ | 585 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://app.driggsby.com/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/app-driggsby-com-mcp # JSON