# Banking Assistant (Metabind demo) (remote · mcp.metabind.ai)

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

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- remote · `mcp.metabind.ai`: 76/100 (this document), [markdown](https://verifymcp.io/servers/ai-metabind-banking-assistant/igjh0bzin4llfncbcdc7-projects-glbhk5i3glliycf63xfl.md), [page](https://verifymcp.io/servers/ai-metabind-banking-assistant/igjh0bzin4llfncbcdc7-projects-glbhk5i3glliycf63xfl)

## Channel facts

- Endpoint: `https://mcp.metabind.ai/IgJH0BzIn4LlfnCbcDc7/projects/GLbHk5i3GLlIYcF63XFl`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.0.17`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-04.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 6159 tokens (~439/item across 14 items; 9 tools + 5 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 86% of tool parameters carry a description.
  - Structured output schemas are declared (44% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the Banking Assistant (Metabind demo) MCP server?

Banking Assistant (Metabind demo) is a hosted endpoint at https://mcp.metabind.ai/IgJH0BzIn4LlfnCbcDc7/projects/GLbHk5i3GLlIYcF63XFl, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ai-metabind-banking-assistant 'https://mcp.metabind.ai/IgJH0BzIn4LlfnCbcDc7/projects/GLbHk5i3GLlIYcF63XFl'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-metabind-banking-assistant": {
      "url": "https://mcp.metabind.ai/IgJH0BzIn4LlfnCbcDc7/projects/GLbHk5i3GLlIYcF63XFl"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-metabind-banking-assistant": {
      "type": "http",
      "url": "https://mcp.metabind.ai/IgJH0BzIn4LlfnCbcDc7/projects/GLbHk5i3GLlIYcF63XFl"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-metabind-banking-assistant]
url = "https://mcp.metabind.ai/IgJH0BzIn4LlfnCbcDc7/projects/GLbHk5i3GLlIYcF63XFl"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-metabind-banking-assistant": {
      "type": "remote",
      "url": "https://mcp.metabind.ai/IgJH0BzIn4LlfnCbcDc7/projects/GLbHk5i3GLlIYcF63XFl",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-metabind-banking-assistant --url 'https://mcp.metabind.ai/IgJH0BzIn4LlfnCbcDc7/projects/GLbHk5i3GLlIYcF63XFl' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-metabind-banking-assistant:
    url: "https://mcp.metabind.ai/IgJH0BzIn4LlfnCbcDc7/projects/GLbHk5i3GLlIYcF63XFl"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-metabind-banking-assistant": {
      "Transport": "http",
      "Url": "https://mcp.metabind.ai/IgJH0BzIn4LlfnCbcDc7/projects/GLbHk5i3GLlIYcF63XFl"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-metabind-banking-assistant -t streamable-http -u 'https://mcp.metabind.ai/IgJH0BzIn4LlfnCbcDc7/projects/GLbHk5i3GLlIYcF63XFl'
```

### Other

```json
{
  "mcpServers": {
    "ai-metabind-banking-assistant": {
      "type": "http",
      "url": "https://mcp.metabind.ai/IgJH0BzIn4LlfnCbcDc7/projects/GLbHk5i3GLlIYcF63XFl"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-04 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-02 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-30 (score 74, 0)

- [cosmetic] Tool “net_worth_trend” changed its title: net_worth_trend → Net Worth Trend
- [cosmetic] Tool “spending_breakdown” changed its title: spending_breakdown → Spending Breakdown
- [cosmetic] Tool “subscriptions” changed its title: subscriptions → Subscriptions
- [cosmetic] Tool “transaction_list” changed its title: transaction_list → Transaction List
- [cosmetic] Tool “trend_card” changed its title: trend_card → Trend Card

### 2026-09-29 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-28 (score 73, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 73)

First indexed and scored.

## MCP tools (9)

### `get_net_worth` (~213 tokens)

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

Input parameters:

- `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…
- `period` (string): How far back the trend goes. Ignored when startDate/endDate are given.
- `startDate` (string): Range start, YYYY-MM-DD. Defaults to a year before endDate.
- `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.

Output parameters:

- `accounts` (array)
- `change` (number)
- `change_pct` (number)
- `current` (number)
- `endDate` (string)
- `groupBy` (string)
- `income` (number)
- `period` (string)
- `periodLabel` (string)
- `points` (array)
- `saved` (number)
- `spending` (number)
- `start` (number)
- `startDate` (string)

### `get_spending_breakdown` (~81 tokens)

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

Input parameters:

- `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.

Output parameters:

- `comparison` (object)
- `groups` (array)
- `net` (number)
- `period` (string)
- `periodLabel` (string)
- `total_income` (number)
- `total_spend` (number)

### `get_subscriptions` (~38 tokens)

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

Input parameters:

- `status` (string): Which subscriptions to include.

Output parameters:

- `count` (integer)
- `new_count` (integer)
- `subscriptions` (array)
- `total_monthly` (number)

### `get_transactions` (~283 tokens)

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

Input parameters:

- `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.
- `endDate` (string): Window end, YYYY-MM-DD. Defaults to today.
- `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.
- `merchant` (string): Single store or brand to filter by, e.g. 'Whole Foods', 'Netflix', 'Shell'. Combine with category to narrow further.
- `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.
- `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.
- `startDate` (string): Window start, YYYY-MM-DD. Defaults to 30 days before endDate.

Output parameters:

- `category` (string)
- `change_vs_prev_pct` (number)
- `count` (integer)
- `periodLabel` (string)
- `shown` (integer)
- `standouts` (array)
- `top_items` (array)
- `total_spent` (number)
- `transactions` (array)

### `net_worth_trend` (~430 tokens)

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.

Input parameters:

- `chartStyle` (string): 'bar' compares periods against each other as closing balances; 'line' is the continuous history.
- `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…
- `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…
- `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 j…
- `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.
- `startDate` (string)

### `spending_breakdown` (~571 tokens)

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.

Input parameters:

- `drillPrompt` (string): 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',…
- `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 m…
- `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…
- `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 j…
- `period` (string): Window: 7d, 30d, mtd (this month so far), lastMonth (the whole previous calendar month), 3mo, 6mo, ytd, 1y or all.

### `subscriptions` (~420 tokens)

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.

Input parameters:

- `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…
- `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 j…
- `status` (string): 'active' lists current subscriptions; 'all' also includes recently cancelled ones.
- `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' i…
- `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']…

### `transaction_list` (~653 tokens)

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.

Input parameters:

- `category` (string): Category or plain term, e.g. 'Food & Dining', 'restaurants', 'rent', 'gas'. Omit for all categories.
- `endDate` (string): Window end, YYYY-MM-DD.
- `limit` (integer): Max transactions to load. Raise past the default 20 only if the user wants the full list.
- `merchant` (string): Single store or brand, e.g. 'Whole Foods', 'Netflix'.
- `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…
- `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 j…
- `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 mtd.
- `startDate` (string): Window start, YYYY-MM-DD.
- `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 norm…
- `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 a…

### `trend_card` (~659 tokens)

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.

Input parameters:

- `change` (number): 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`, w…
- `change_pct` (number)
- `chartStyle` (string): '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.
- `current` (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 nam…
- `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…
- `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 j…
- `periodLabel` (string)
- `points` (array)
- `start` (number)
- `title` (string)
- `upIsGood` (boolean): false for cost-like metrics: an increase renders red, a decrease green.
- `valueFormat` (string): How the hero value and change are formatted.
- `valueSuffix` (string): Optional unit appended to values, e.g. ' subs' or '/mo'.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-metabind-banking-assistant/igjh0bzin4llfncbcdc7-projects-glbhk5i3glliycf63xfl#diagnostics

## Score history

- 2026-10-04: 76
- 2026-10-03: 75
- 2026-10-02: 75
- 2026-10-01: 74
- 2026-09-30: 74
- 2026-09-29: 74
- 2026-09-28: 73
- 2026-09-27: 73

## Common questions

### What is the Banking Assistant (Metabind demo) MCP server?

Banking Assistant (Metabind demo) is an MCP server listed in the public MCP registry as ai.metabind/banking-assistant. Demo personal-finance MCP App: spending, subscriptions, and net worth as interactive UI. This page covers its hosted endpoint (https://mcp.metabind.ai/IgJH0BzIn4LlfnCbcDc7/projects/GLbHk5i3GLlIYcF63XFl).

### Is the Banking Assistant (Metabind demo) MCP server safe to use?

Banking Assistant (Metabind demo) scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Banking Assistant (Metabind demo) MCP server expose?

Banking Assistant (Metabind demo) exposes 9 tools: get_net_worth, get_spending_breakdown, get_subscriptions, get_transactions, net_worth_trend, and 4 more. Their descriptions and schemas cost roughly 3,348 tokens of context every time the server is loaded.

### Does the Banking Assistant (Metabind demo) MCP server require authentication?

No. We connected to Banking Assistant (Metabind demo) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Banking Assistant (Metabind demo) MCP server still maintained?

Banking Assistant (Metabind demo) is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.metabind.ai/IgJH0BzIn4LlfnCbcDc7/projects/GLbHk5i3GLlIYcF63XFl
- Repository: https://github.com/metabindai/metabind-demos
- Website: https://www.metabind.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-metabind-banking-assistant/igjh0bzin4llfncbcdc7-projects-glbhk5i3glliycf63xfl.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-metabind-banking-assistant/igjh0bzin4llfncbcdc7-projects-glbhk5i3glliycf63xfl.json
- HTML version of this page: https://verifymcp.io/servers/ai-metabind-banking-assistant/igjh0bzin4llfncbcdc7-projects-glbhk5i3glliycf63xfl