Model Context Protocol (MCP) server for freee API integration
NZ Open Banking (Akahu) is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Ask about your NZ bank accounts via Akahu open finance. Read-only by default, consent per write.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'AKAHU_USER_TOKEN=${AKAHU_USER_TOKEN}' --env 'AKAHU_APP_TOKEN=${AKAHU_APP_TOKEN}' --transport stdio nz-open-banking-akahu-mcp '--' uvx nz-openbank-mcp
# 2 — ask your agent for something these tools do
# list_accounts, get_account, get_pending_transactions and 24 more
It needs AKAHU_USER_TOKEN, AKAHU_APP_TOKEN: this reads them from your environment, so export them first.
NZ Open Banking (Akahu) costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts NZ Open Banking (Akahu) as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads AKAHU_USER_TOKEN (User token from https://my.akahu.nz/developers), AKAHU_APP_TOKEN (App token from https://my.akahu.nz/developers) from your environment each time it starts the server, so the value stays out of its config: export them in your shell profile (macOS, Linux), or run setx AKAHU_USER_TOKEN …, setx AKAHU_APP_TOKEN … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'AKAHU_USER_TOKEN=${AKAHU_USER_TOKEN}' --env 'AKAHU_APP_TOKEN=${AKAHU_APP_TOKEN}' --transport stdio nz-open-banking-akahu-mcp '--' uvx nz-openbank-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
It reaches a system of yours, so it needs your own credential rather than the publisher’s: AKAHU_USER_TOKEN — User token from https://my.akahu.nz/developers.; AKAHU_APP_TOKEN — App token from https://my.akahu.nz/developers.. You set them in your own client’s config, on your machine — this marketplace never holds it.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
27 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
List every connected account with masked numbers and formatted balances.
Takes no parameters.
Fetch a single account by id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account_id | string | yes | Akahu account id (e.g. "acc_chq_001"). |
List pending (not-yet-settled) transactions for one account.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account_id | string | yes | Akahu account id. |
Return just the balance for an account. Cheaper than get_account.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account_id | string | yes | Akahu account id. |
Trigger Akahu to fetch fresh data for every connected account.
Takes no parameters.
Trigger Akahu to fetch fresh data for one specific account.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account_id | string | yes | Akahu account id to refresh. |
Return identity/profile data for the connected Akahu user.
Takes no parameters.
Verify a name against the account holder via Akahu's identity check.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| family_name | string | yes | Required. Surname to verify. |
| given_name | string | no | Optional first name. |
| middle_name | string | no | Optional middle name. |
| initials | array | no | Optional list of initial strings (e.g. ["J", "R"]). |
| account_id | string | no | Optional account scope; omit to check all sources. |
List settled transactions with optional filters.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account_id | string | no | Scope to one account (sent to Akahu). |
| start_date | string | no | Earliest NZ day as YYYY-MM-DD (inclusive), or an ISO 8601 timestamp passed to Akahu as an exclusive lower bound (UTC if it has no offset). |
| end_date | string | no | Latest NZ day as YYYY-MM-DD (inclusive), or an ISO 8601 timestamp passed to Akahu as an inclusive upper bound (UTC if it has no offset). |
| category | string | no | Exact category name (applied after fetching). |
| min_amount | no | Lower bound on signed amount (applied after fetching; negatives are debits). | |
| max_amount | no | Upper bound on signed amount (applied after fetching). | |
| limit | no | Max items returned, 1 to 500 (default 100). |
Fetch one settled transaction by id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| transaction_id | string | yes | Akahu transaction id (e.g. "txn_a1b2c3"). |
Batch-fetch settled transactions by their ids in one request.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ids | array | yes | List of Akahu transaction ids. |
Case-insensitive substring search across description and merchant name.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Substring to match (case-insensitive). |
| start_date | string | no | Earliest NZ day as YYYY-MM-DD (inclusive) or an ISO 8601 timestamp (UTC if it has no offset); defaults to 90 days back. |
| end_date | string | no | Latest NZ day as YYYY-MM-DD (inclusive) or an ISO 8601 timestamp (UTC if it has no offset); defaults to no upper bound. |
| limit | no | Max matches returned, 1 to 500 (default 50). |
Submit a support ticket about a transaction to Akahu staff.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| transaction_id | string | yes | Akahu transaction id the ticket is about. |
| issue_type | yes | One of "DUPLICATE", "ENRICHMENT_ERROR", "ENRICHMENT_SUGGESTION". | |
| fields | array | no | Affected field names; required for ENRICHMENT_* issue types. Omitted -> the user is prompted to supply them via elicitation. |
| comment | string | no | Optional free-text context for the support agent, up to 1,000 characters. |
| other_transaction_id | string | no | Paired transaction id; required for DUPLICATE. Omitted -> the user is prompted to supply it via elicitation. |
Every connected account, with masked numbers and balances
No parameter schema on file.
One account by id
No parameter schema on file.
Just the balance of one account
No parameter schema on file.
Unsettled transactions for one account
No parameter schema on file.
Ask Akahu to fetch fresh data for every account (write)
No parameter schema on file.
Ask Akahu to fetch fresh data for one account (write)
No parameter schema on file.
Settled transactions filtered by account, dates, category or amount
No parameter schema on file.
One transaction by id
No parameter schema on file.
Several transactions in one request
No parameter schema on file.
Unsettled transactions across all accounts
No parameter schema on file.
Text search over description and merchant
No parameter schema on file.
Open a support ticket with Akahu about a transaction (write)
No parameter schema on file.
The Akahu user's profile
No parameter schema on file.
Check a name against the account holder (write, extra scope)
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under Apache-2.0
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install NZ Open Banking (Akahu) or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (13 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_accounts | no tags | |
| get_account | untrusted-input | untrusted-input: keyword "fetch" |
| get_pending_transactions | no tags | |
| get_account_balance | no tags | |
| refresh_all_accounts | untrusted-input | untrusted-input: keyword "fetch" |
| refresh_account | untrusted-input | untrusted-input: keyword "fetch" |
| get_me | no tags | |
| verify_name | no tags | |
| get_transactions | no tags | |
| get_transaction | untrusted-input | untrusted-input: keyword "fetch" |
| get_transactions_by_ids | untrusted-input | untrusted-input: keyword "fetch" |
| search_transactions | no tags | |
| report_transaction_issue | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.7. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish NZ Open Banking (Akahu) can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.