Banking Assistant (Metabind demo)

Working · 2.7 s

ai.metabind/banking-assistantv0.0.17 Domain verified

Demo personal-finance MCP App: spending, subscriptions, and net worth as interactive UI.

Finance & Payments

Source Website Registry entry

Maintain this server? Claim it

Try it

Call this server's tools from your browser. Nothing to install.

https://mcp.metabind.ai/IgJH0BzIn4LlfnCbcDc7/projects/GLbHk5i3GLlIYcF63XFl

Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.

Tool list from our last check. Connect live to refresh it.

get_net_worth Read-only

Net worth history + account balances. Numbers to reason with — to display, use net_worth_trend.

periodstring

How far back the trend goes. Ignored when startDate/endDate are given.

endDatestring

Range end, YYYY-MM-DD. Defaults to today.

groupBystring

Granularity of the returned series. Each point carries that period's CLOSING balance. 'auto' picks a readable granularity for the span; set it explicitly to compare periods against each other — 'year' over a two-year range gives one point per year, 'month' gives one per month.

summaryboolean

Omit the `points` series and return only the headline figures and accounts. Use this when you want the numbers to comment on rather than to chart — it is a fraction of the size of a full result.

startDatestring

Range start, YYYY-MM-DD. Defaults to a year before endDate.

Tools (9)

get_net_worth

Net worth history + account balances. Numbers to reason with — to display, use net_worth_trend.

read-only

Argument	Type	Description
period	string	How far back the trend goes. Ignored when startDate/endDate are given.
endDate	string	Range end, YYYY-MM-DD. Defaults to today.
groupBy	string	Granularity of the returned series. Each point carries that period's CLOSING balance. 'auto' picks a readable granularity for the span; set it explicitly to compare periods against each other — 'year' over a two-year range gives one point per year, 'month' gives one per month.
summary	boolean	Omit the `points` series and return only the headline figures and accounts. Use this when you want the numbers to comment on rather than to chart — it is a fraction of the size of a full result.
startDate	string	Range start, YYYY-MM-DD. Defaults to a year before endDate.

Input schema (JSON)

{
  "type": "object",
  "required": [],
  "properties": {
    "period": {
      "enum": [
        "7d",
        "30d",
        "mtd",
        "lastMonth",
        "3mo",
        "6mo",
        "ytd",
        "1y",
        "all"
      ],
      "type": "string",
      "default": "1y",
      "description": "How far back the trend goes. Ignored when startDate/endDate are given."
    },
    "endDate": {
      "type": "string",
      "description": "Range end, YYYY-MM-DD. Defaults to today."
    },
    "groupBy": {
      "enum": [
        "auto",
        "day",
        "week",
        "month",
        "quarter",
        "year"
      ],
      "type": "string",
      "default": "auto",
      "description": "Granularity of the returned series. Each point carries that period's CLOSING balance. 'auto' picks a readable granularity for the span; set it explicitly to compare periods against each other — 'year' over a two-year range gives one point per year, 'month' gives one per month."
    },
    "summary": {
      "type": "boolean",
      "default": false,
      "description": "Omit the `points` series and return only the headline figures and accounts. Use this when you want the numbers to comment on rather than to chart — it is a fraction of the size of a full result."
    },
    "startDate": {
      "type": "string",
      "description": "Range start, YYYY-MM-DD. Defaults to a year before endDate."
    }
  },
  "additionalProperties": false
}

get_spending_breakdown

Categorized spending + prior-period comparison. Numbers to reason with — to display, use spending_breakdown.

read-only

Argument	Type	Description
period	string	Spending window.
summary	boolean	Drop each category's top_merchants list and return only the headline totals and per-category amounts. Use this when you want the numbers to comment on rather than to chart.

Input schema (JSON)

{
  "type": "object",
  "required": [],
  "properties": {
    "period": {
      "enum": [
        "7d",
        "30d",
        "mtd",
        "lastMonth",
        "3mo",
        "6mo",
        "ytd",
        "1y",
        "all"
      ],
      "type": "string",
      "default": "mtd",
      "description": "Spending window."
    },
    "summary": {
      "type": "boolean",
      "default": false,
      "description": "Drop each category's top_merchants list and return only the headline totals and per-category amounts. Use this when you want the numbers to comment on rather than to chart."
    }
  },
  "additionalProperties": false
}

get_subscriptions

Recurring-charge detection. Numbers to reason with — to display, use the subscriptions card.

read-only

Argument	Type	Description
status	string	Which subscriptions to include.

Input schema (JSON)

{
  "type": "object",
  "required": [],
  "properties": {
    "status": {
      "enum": [
        "active",
        "all"
      ],
      "type": "string",
      "default": "active",
      "description": "Which subscriptions to include."
    }
  },
  "additionalProperties": false
}

get_transactions

Raw transactions by category or merchant, ~12 months of history. Numbers to reason with — to display, use transaction_list.

read-only

Argument	Type	Description
sort	string	'recent' is newest-first and is what a plain list wants. Use 'largest' for "my biggest transactions" — a window can hold hundreds of rows, so date order buries them.
limit	integer	Max transactions to return. Pass 0 for totals and counts only — much cheaper when you need the figures to reason with rather than to list.
period	string	Time window. Ignored when startDate/endDate are given. The feed covers ~25 months, so a 1y window has a full prior year to compare against.
endDate	string	Window end, YYYY-MM-DD. Defaults to today.
category	string	Category or plain term to filter by, e.g. 'Food & Dining', 'restaurants', 'rent', 'gas', 'income'. A merchant name here is resolved as a merchant. Omit or leave empty for all categories.
merchant	string	Single store or brand to filter by, e.g. 'Whole Foods', 'Netflix', 'Shell'. Combine with category to narrow further.
startDate	string	Window start, YYYY-MM-DD. Defaults to 30 days before endDate.

net_worth_trend

Render net_worth_trend: Net worth: current total, change over the period, a trend chart, and the account balances behind it. It loads its own data. To compare periods against each other pass chartStyle:'bar' plus groupBy ('year' for this-year-vs-last-year, 'month' for month-by-month) — each bar is that period's closing balance.

read-only

Argument	Type	Description
note	string	Usually omit this. Optional one-line insight rendered inside the card. Only pass it when you ALREADY have the figures in hand from a call you made for another reason — never make an extra tool call just to write a note, because that round trip delays the card itself. When you do add one, say something the card does not already show (what drove a change, what to watch), in one sentence, and never guess a number.
period	string	Window: 7d, 30d, mtd (this month so far), lastMonth (the whole previous calendar month), 3mo, 6mo, ytd, 1y or all. Ignored when startDate/endDate are given. Defaults to 1y.
endDate	string
groupBy	string	One bar/point per period, carrying that period's closing balance. Set it to compare periods: 'year' for "this year vs last year", 'month' for "month by month", 'quarter' for "by quarter". Leave auto for a plain trend.
nextSteps	array	One short follow-up the user might ask next, in the form icon\|question — 'calendar\|Show me last month'. Phrase the question the way the user would say it, and take the icon from the table in the app instructions; any other name renders blank. Always supply 2-3. The card itself ignores them.

spending_breakdown

Render spending_breakdown: Spending split by category for a period: a composition bar plus a ranked category list. It loads its own data — pass the period alone for the whole picture, which is what a broad 'where did my money go' question wants. Use highlight only on a follow-up about particular categories; it dims everything else, so on an opening question it hides most of the answer.

read-only

Argument	Type	Description
note	string	Usually omit this. Optional one-line insight rendered inside the card. Only pass it when you ALREADY have the figures in hand from a call you made for another reason — never make an extra tool call just to write a note, because that round trip delays the card itself. When you do add one, say something the card does not already show (what drove a change, what to watch), in one sentence, and never guess a number.
period	string	Window: 7d, 30d, mtd (this month so far), lastMonth (the whole previous calendar month), 3mo, 6mo, ytd, 1y or all.
highlight	array	OMIT THIS unless the user asked about specific categories. Leaving it empty is the normal, correct view: the whole picture, nothing dimmed. A broad opening question — 'where did my money go', 'show me my spending', 'how did I do this month' — wants the whole picture, so pass period alone. Only emphasise on a FOLLOW-UP that is genuinely about particular categories ('what should I cut', 'is dining out of hand', 'why is it higher than last month'), where you name them: ['Food & Dining','Subscriptions']. Everything else then dims and the hero reports their combined total. Matching is forgiving ('dining' finds 'Food & Dining').
nextSteps

subscriptions

Render subscriptions: Recurring charges: total monthly cost and a row per subscription with its cadence, next charge date, and New / price-increase flags. It loads its own data.

read-only

Argument	Type	Description
note	string	Usually omit this. Optional one-line insight rendered inside the card. Only pass it when you ALREADY have the figures in hand from a call you made for another reason — never make an extra tool call just to write a note, because that round trip delays the card itself. When you do add one, say something the card does not already show (what drove a change, what to watch), in one sentence, and never guess a number.
view	string	Which cut to open on. 'all' is every recurring charge, biggest first — the answer to 'what am I paying for'. 'repriced' is only the ones whose price moved, which is what 'which went up' asks. 'new' is only the recently started. 'unusual' is both of those together, for a general 'anything odd'. Match the cut to the question: a price question answered with the full list makes the user hunt for the answer. The header keeps reporting the full count, so narrowing hides nothing.
views	array	Which cuts to offer as segments. Omit and the card offers All alongside whichever cut you opened on. Pair the specific cut with 'all' so the user can get back to the full picture — ['all','repriced'] for a price question, ['all','new'] for a what's-new one.
status	string	'active' lists current subscriptions; 'all' also includes recently cancelled ones.
nextSteps

transaction_list

Render transaction_list: Individual purchases for a category or a merchant: the window total plus the matching transactions. It loads its own data. Plain terms like 'restaurants', 'groceries' or 'gas' resolve to categories; omit both filters for all spending. Do NOT use this when the user asks how much they spent over the last 3, 6 or 12 months — that is a period comparison, so use trend_card with chartStyle:'bar' instead.

read-only

Argument	Type	Description
note	string	Usually omit this. Optional one-line insight rendered inside the card. Only pass it when you ALREADY have the figures in hand from a call you made for another reason — never make an extra tool call just to write a note, because that round trip delays the card itself. When you do add one, say something the card does not already show (what drove a change, what to watch), in one sentence, and never guess a number.
view	string	Which cut of the window to open on. 'recent' is newest-first, the plain list. 'largest' leads with the biggest charges. 'unusual' shows only the charges well above what that merchant or category normally costs — this is the answer to "anything odd this month", not a spending breakdown. The user can switch between the offered cuts on the card without asking again, so pick the one that answers the question and leave the rest to them. Use `views` to change which cuts are offered.
limit	integer	Max transactions to load. Raise past the default 20 only if the user wants the full list.
views	array	Which cuts to offer as segments on the card. Omit for all three, which is usually right — the user can then explore without asking again. Narrow it only when a cut would be meaningless for what was asked: a single-merchant list has little to call unusual, and a one-week window has little to rank. Listing a single cut drops the control entirely and renders a plain list, so use that when the question has exactly one sensible answer.

trend_card

Render trend_card: Any metric over time that has no dedicated card — one category's spend by month, a series you computed. Points are {label, value} in display order. Set upIsGood=false for cost-like metrics. Use chartStyle:'bar' whenever the user compares periods — month by month, or over the last 3/6/12 months; give each point a `series` name (repeating the label once per series) to stack them with a legend. Pass `items` to list the composition behind the number.

read-only

Argument	Type	Description
note	string	Usually omit this. Optional one-line insight rendered inside the card. Only pass it when you ALREADY have the figures in hand from a call you made for another reason — never make an extra tool call just to write a note, because that round trip delays the card itself. When you do add one, say something the card does not already show (what drove a change, what to watch), in one sentence, and never guess a number.
items	array	Optional rows under the chart — the composition behind the number (accounts behind a net worth, categories behind a month's spend). Each is { name, detail, value, color?, prompts? }. `color` is a named colour for the dot ('blue', 'green', …); omit it and rows are coloured in order. `prompts` are follow-up questions offered when the row is tapped — each string is shown as the menu label AND sent to the assistant verbatim, so keep them short and self-contained ('How has my Brokerage changed?', not 'changed?'). OMIT `prompts` unless a row needs something its name cannot imply: left out, the card builds its own drill-down from `name`, which saves you writing the same sentence once per row.
start	number
title

{ "type": "object", "required": [], "properties": { "note": { "type": "string", "default": "", "description": "Usually omit this. Optional one-line insight rendered inside the card. Only pass it when you ALREADY have the figures in hand from a call you made for another reason — never make an extra tool call just to write a note, because that round trip delays the card itself. When you do add one, say something the card does not already show (what drove a change, what to watch), in one sentence, and never guess a number." }, "period": { "type": "string", "default": "mtd", "description": "Window: 7d, 30d, mtd (this month so far), lastMonth (the whole previous calendar month), 3mo, 6mo, ytd, 1y or all." }, "highlight": { "type": "array", "items": { "type": "string" }, "description": "OMIT THIS unless the user asked about specific categories. Leaving it empty is the normal, correct view: the whole picture, nothing dimmed. A broad opening question — 'where did my money go', 'show me my spending', 'how did I do this month' — wants the whole picture, so pass period alone. Only emphasise on a FOLLOW-UP that is genuinely about particular categories ('what should I cut', 'is dining out of hand', 'why is it higher than last month'), where you name them: ['Food & Dining','Subscriptions']. Everything else then dims and the hero reports their combined total. Matching is forgiving ('dining' finds 'Food & Dining')." }, "nextSteps": { "type": "array", "items": { "type": "string" }, "description": "One short follow-up the user might ask next, in the form icon|question — 'calendar|Show me last month'. Phrase the question the way the user would say it, and take the icon from the table in the app instructions; any other name renders blank. Always supply 2-3. The card itself ignores them." }, "drillPrompt": { "type": "string", "default": "", "description": "What tapping a category should ask, when the question had an angle worth carrying. Write it as the user would say it and put {category} where the name goes: 'Show me the odd {category} transactions', 'Where can I cut back on {category}?'. Set it when the card answers something pointed — unusual spending, what to cut, why something moved — so the follow-up inherits that instead of resetting to a plain list. Omit it for a broad 'where did my money go', where a plain list is what a tap should give." } }, "description": "Spending split by category for a period: a composition bar plus a ranked category list. It loads its own data — pass the period alone for the whole picture, which is what a broad 'where did my money go' question wants. Use highlight only on a follow-up about particular categories; it dims everything else, so on an opening question it hides most of the answer.", "additionalProperties": false }

{ "type": "object", "required": [], "properties": { "note": { "type": "string", "default": "", "description": "Usually omit this. Optional one-line insight rendered inside the card. Only pass it when you ALREADY have the figures in hand from a call you made for another reason — never make an extra tool call just to write a note, because that round trip delays the card itself. When you do add one, say something the card does not already show (what drove a change, what to watch), in one sentence, and never guess a number." }, "view": { "enum": [ "recent", "largest", "unusual" ], "type": "string", "default": "recent", "description": "Which cut of the window to open on. 'recent' is newest-first, the plain list. 'largest' leads with the biggest charges. 'unusual' shows only the charges well above what that merchant or category normally costs — this is the answer to \"anything odd this month\", not a spending breakdown. The user can switch between the offered cuts on the card without asking again, so pick the one that answers the question and leave the rest to them. Use `views` to change which cuts are offered." }, "limit": { "type": "integer", "default": 0, "description": "Max transactions to load. Raise past the default 20 only if the user wants the full list." }, "views": { "type": "array", "items": { "enum": [ "recent", "largest", "unusual" ], "type": "string" }, "description": "Which cuts to offer as segments on the card. Omit for all three, which is usually right — the user can then explore without asking again. Narrow it only when a cut would be meaningless for what was asked: a single-merchant list has little to call unusual, and a one-week window has little to rank. Listing a single cut drops the control entirely and renders a plain list, so use that when the question has exactly one sensible answer." }, "period": { "type": "string", "default": "", "description": "Window: 7d, 30d, mtd (this month so far), lastMonth (the whole previous calendar month), 3mo, 6mo, ytd, 1y or all. Ignored when startDate/endDate are given. Defaults to mtd." }, "endDate": { "type": "string", "default": "", "description": "Window end, YYYY-MM-DD." }, "category": { "type": "string", "default": "", "description": "Category or plain term, e.g. 'Food & Dining', 'restaurants', 'rent', 'gas'. Omit for all categories." }, "merchant": { "type": "string", "default": "", "description": "Single store or brand, e.g. 'Whole Foods', 'Netflix'." }, "nextSteps": { "type": "array", "items": { "type": "string" }, "description": "One short follow-up the user might ask next, in the form icon|question — 'calendar|Show me last month'. Phrase the question the way the user would say it, and take the icon from the table in the app instructions; any other name renders blank. Always supply 2-3. The card itself ignores them." }, "startDate": { "type": "string", "default": "", "description": "Window start, YYYY-MM-DD." } }, "description": "Individual purchases for a category or a merchant: the window total plus the matching transactions. It loads its own data. Plain terms like 'restaurants', 'groceries' or 'gas' resolve to categories; omit both filters for all spending. Do NOT use this when the user asks how much they spent over the last 3, 6 or 12 months — that is a period comparison, so use trend_card with chartStyle:'bar' instead.", "additionalProperties": false }

{ "type": "object", "required": [], "properties": { "note": { "type": "string", "default": "", "description": "Usually omit this. Optional one-line insight rendered inside the card. Only pass it when you ALREADY have the figures in hand from a call you made for another reason — never make an extra tool call just to write a note, because that round trip delays the card itself. When you do add one, say something the card does not already show (what drove a change, what to watch), in one sentence, and never guess a number." }, "items": { "type": "array", "items": { "type": "object", "properties": { "name": { "type": "string" }, "color": { "type": "string" }, "value": { "type": "number" }, "detail": { "type": "string" }, "prompts": { "type": "array", "items": { "type": "string" } } } }, "description": "Optional rows under the chart — the composition behind the number (accounts behind a net worth, categories behind a month's spend). Each is { name, detail, value, color?, prompts? }. `color` is a named colour for the dot ('blue', 'green', …); omit it and rows are coloured in order. `prompts` are follow-up questions offered when the row is tapped — each string is shown as the menu label AND sent to the assistant verbatim, so keep them short and self-contained ('How has my Brokerage changed?', not 'changed?'). OMIT `prompts` unless a row needs something its name cannot imply: left out, the card builds its own drill-down from `name`, which saves you writing the same sentence once per row." }, "start": { "type": "number", "default": 0 }, "title": { "type": "string", "default": "Trend" }, "change": { "type": "number", "default": 0, "description": "The change over the period, in the same unit as `current`. Send it together with `start` whenever you have them: the card leads with this figure, and left out it has to work back from `change_pct`, which is close but not the real number." }, "points": { "type": "array", "items": { "type": "object", "properties": { "label": { "type": "string" }, "value": { "type": "number" }, "series": { "type": "string" } } } }, "current": { "type": "number", "default": 0 }, "upIsGood": { "type": "boolean", "default": true, "description": "false for cost-like metrics: an increase renders red, a decrease green." }, "nextSteps": { "type": "array", "items": { "type": "string" }, "description": "One short follow-up the user might ask next, in the form icon|question — 'calendar|Show me last month'. Phrase the question the way the user would say it, and take the icon from the table in the app instructions; any other name renders blank. Always supply 2-3. The card itself ignores them." }, "change_pct": { "type": "number", "default": 0 }, "chartStyle": { "enum": [ "line", "bar" ], "type": "string", "default": "line", "description": "'bar' draws discrete bars on a labelled x axis — better for comparing periods against each other, and the only style that stacks series. 'line' is the continuous trend." }, "periodLabel": { "type": "string", "default": "Past 12 months" }, "valueFormat": { "enum": [ "currency", "number" ], "type": "string", "default": "currency", "description": "How the hero value and change are formatted." }, "valueSuffix": { "type": "string", "default": "", "description": "Optional unit appended to values, e.g. ' subs' or '/mo'." } }, "description": "Any metric over time that has no dedicated card — one category's spend by month, a series you computed. Points are {label, value} in display order. Set upIsGood=false for cost-like metrics. Use chartStyle:'bar' whenever the user compares periods — month by month, or over the last 3/6/12 months; give each point a `series` name (repeating the label once per series) to stack them with a legend. Pass `items` to list the composition behind the number.", "additionalProperties": false }