Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
Enable Banking 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.
100/100
trust score
18
downloads a day
local
runs on your machine
333
downloads in 30d
What it does
Read, search and export statements and balances from banks across Europe, without moving money.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'ENABLE_BANKING_CONFIG=${ENABLE_BANKING_CONFIG}' --transport stdio enable-banking-mcp '--' npx -y @foreverworks/mcp-enable-banking
# 2 — ask your agent for something these tools do
# list_stored_sessions, list_accounts, get_transactions and 7 more
It needs ENABLE_BANKING_CONFIG: this reads it from your environment, so export it first.
Enable Banking costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
FOAll 6 servers
foreverworks6 servers
3 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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 Enable Banking 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.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads ENABLE_BANKING_CONFIG (Path of app.json: your Enable Banking application's id, its redirect URL and the name of its private key file, as the README describes it) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx ENABLE_BANKING_CONFIG … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'ENABLE_BANKING_CONFIG=${ENABLE_BANKING_CONFIG}' --transport stdio enable-banking-mcp '--' npx -y @foreverworks/mcp-enable-bankingReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs settings only you can give it: ENABLE_BANKING_CONFIG — Path of app.json: your Enable Banking application's id, its redirect URL and the name of its private key file, as the README describes it.. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
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.
What you approve
10 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.
Every stored consent: its label, the bank, the accounts it covered, and when it EXPIRES (date and
No parameter schema on file.
The accounts a stored consent currently reaches, asked of the API rather than replayed from
| Parameter | Type | Required | Notes |
|---|---|---|---|
| label | string | no | A label from list_stored_sessions; may be left out when only one consent is stored. |
A statement: the transactions of one account (account_uid), of every account on one consent (label),
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account_uid | string | no | One account: the uid field from list_accounts (a UUID, not the IBAN). Leave out to read every account on a consent. |
| label | string | no | Every account on this stored consent (a label from list_stored_sessions). Leave out, with account_uid, to read every stored consent. |
| date_from | string | no | YYYY-MM-DD, inclusive. |
| date_to | string | no | YYYY-MM-DD, inclusive. |
| transaction_status | string | no | — |
| text | string | no | Keep rows whose counterparty name or IBAN, payment reference or entry reference contains this; case and diacritics ignored. |
| direction | string | no | credit: money in; debit: money out. |
| amount_min | string | no | Keep rows of at least this size, sign ignored, as a plain decimal such as "250" or "1200.50". |
| amount_max | string | no | Keep rows of at most this size, sign ignored. |
The same statement as get_transactions (same arguments, same filters, same reads at the bank), written
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account_uid | string | no | One account: the uid field from list_accounts (a UUID, not the IBAN). Leave out to read every account on a consent. |
| label | string | no | Every account on this stored consent (a label from list_stored_sessions). Leave out, with account_uid, to read every stored consent. |
| date_from | string | no | YYYY-MM-DD, inclusive. |
| date_to | string | no | YYYY-MM-DD, inclusive. |
| transaction_status | string | no | — |
| text | string | no | Keep rows whose counterparty name or IBAN, payment reference or entry reference contains this; case and diacritics ignored. |
| direction | string | no | credit: money in; debit: money out. |
| amount_min | string | no | Keep rows of at least this size, sign ignored, as a plain decimal such as "250" or "1200.50". |
| amount_max | string | no | Keep rows of at most this size, sign ignored. |
The balances the bank reports for one account uid: every type it sends (booked, available, interim,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account_uid | string | yes | The uid field from list_accounts (a UUID, not the IBAN). |
Begin a consent with one bank, valid for … days, over every account the bank offers.
No parameter schema on file.
Exchange the code from the bank's redirect for a session and store it under label, replacing the consent
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code_or_url | string | yes | The full redirect URL (...?code=...&state=...), or the code value alone. |
| label | string | no | — |
End a stored consent: Enable Banking is asked to close the session, which ends the bank's consent, and
| Parameter | Type | Required | Notes |
|---|---|---|---|
| label | string | yes | The consent to end, as list_stored_sessions names it. |
Check that the integration is alive and say so in detail: the Enable Banking application the
No parameter schema on file.
List the banks Enable Banking can reach, by two-letter country code. The name field is what
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | yes | Two-letter code, like RO. Empty means every market, a large answer. |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- 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 Enable Banking or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 100 / 100
Release 0.1.0 · scanned 28 Oct 2026
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.
Threat score100
Client score100
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationsource
Surface digest1d88b8e7b253b925ccfeca1c52094781183c10a1987544f78112ac3b2967bc93
Score vectorthreat 100 → client 100
| 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 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
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.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (10 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_stored_sessions | no tags | |
| list_accounts | no tags | |
| get_transactions | no tags | |
| export_transactions | no tags | |
| get_balances | no tags | |
| start_auth | no tags | |
| complete_auth | no tags | |
| revoke_session | no tags | |
| health | no tags | |
| list_aspsps | 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
Integrityfirst-seen
Surface digest1d88b8e7b253b925
Scanned2026-10-28
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.0. Pin a release below and the command asks for exactly that one.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish Enable Banking can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.