A production-ready Model Context Protocol (MCP) server for private personal finance management.
Finance Intelligence MCP has 9 tools with complete input schemas and descriptions, but quality is inconsistent. Tool names follow verb_noun convention (add_expense, list_expenses, etc.), which is good. However, descriptions vary widely in clarity and actionability. Most parameter descriptions are present but lack constraint details (enums, ranges, formats). Output schemas are not documented, LLMs cannot predict response structure. Error handling is minimal; no recovery guidance or actionable error messages visible in code. The server uses PostgreSQL with user authentication, which is secure, but no audit logging or permission gates are evident. Composition is reasonable (each tool has one responsibility), but some tools like update_budgets and delete_budgets accept both ID-based and filter-based selection, creating ambiguity.
Add an expense to the database.
Create one or more budgets for expense tracking and monitoring.
Delete one or more budgets. Supports filtering by budget IDs or multiple criteria.
Summarize and breakdown expenses by columns or time units within a date range.
Generate expense analytics with optional grouping by period and/or category/subcategory. Returns a chart visualization and detailed breakdown data.
Calculate a comprehensive financial health score based on budget adherence, expense stability, savings capacity, category balance, and large expense ratio. Returns individual KPI scores with explanations.
Output schemas not documented. LLMs cannot predict response structure for any tool. list_expenses returns dict with 'status', 'message', 'export_url', 'data' on large results, but plain array on small results, inconsistent and undocumented.
Parameter constraints missing. 'group_by' in expense_breakdown accepts 'category', 'subcategory', 'note', 'date' but no enum constraint. 'breakdown' accepts 'day', 'month', 'year' but undocumented. LLMs will hallucinate invalid values.
update_budgets and delete_budgets accept both 'budget_ids' array AND filter parameters (filter_budget_type, filter_category, etc.), creating ambiguity. If both are provided, which takes precedence? Undocumented dependency.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 57 | 2026-07-28+ | v2 |
List budgets with optional filtering by type, category, subcategory, or period.
List all expenses from the database within a date range (inclusive). If the list contains more than 50 items, it truncates the inline results to the first 50 and exports the full dataset to a downloadable CSV spreadsheet.
Update one or more budgets with new values. Supports filtering by budget IDs or multiple criteria.
No error handling guidance. Code does not show error responses, recovery hints, or actionable messages. If date parsing fails or database connection drops, LLM receives no guidance on retry strategy.
Destructive operations (delete_budgets) lack confirmation or dry-run support. An agent could delete all budgets matching a filter with no undo mechanism.