The security model, in full.

This page is the long version of the landing's security section — written for the person deciding whether to let an AI assistant near an account. It describes what the connector can see, what it can do, which switches control that, and where the sandbox ends. Every claim below maps to a concrete mechanism you can inspect: the connector is an MCP server you run yourself, configured by environment variables you set yourself.

The principle: locked down by default

The connector is configured for read-only access by default. Enabling a write requires a deliberate change to its local configuration. That configuration control is separate from the authentication, authorisation and verification requirements that apply to a live Satchel service.

The configuration controls sit outside the model. They are intended to help you decide which connector capabilities you permit; they do not replace your own review or the controls that apply to the live service.

Read-only by default

Six of the seven tools only read: accounts, balances, cards, transactions, a single payment, a cash-flow summary. The seventh, satchel_move_money, is the only tool that can request a change. In the current connector release it checks forSATCHEL_ALLOW_WRITES=true in the connector's environment before sending a transfer request. Review that setting and the request before enabling it.

The connector's local write setting is not a substitute for the controls applicable to a live service. Any access to live credentials is subject to the relevant account agreement and to applicable authentication, authorisation and verification procedures.

What your assistant sees

The MCP server runs locally, on your machine, with your credentials. When a tool returns account data, that data flows into your assistant's context — Claude, Cursor, whatever you connected — under your agreement with your AI provider. The connector is designed so that:

• This site and the connector do not operate an LLM. The connector does not send account data to a model on Satchel's behalf.
• Your conversations with an AI provider are governed by that provider's terms and privacy information.
• Which tool results your assistant retains, and for how long, is governed by your AI provider's terms — read them with the same care you're reading this.

Sessions and credentials

The connector authenticates with your credentials and receives a session token that has a limited lifetime. When it expires, the connector can request a new session in accordance with the service configuration. Do not place credentials in prompts or chat transcripts.

Configuration lives in environment variables on your machine — SATCHEL_BASE_URL, SATCHEL_USERNAME, SATCHEL_PASSWORD, SATCHEL_MODE — set once in your MCP client config. Protect those values as credentials. The connector is designed to keep this configuration local to the machine on which you run it.

The sandbox boundary

You start against seeded, synthetic data — accounts, cards and a ledger that are live-shaped but fictional. No real funds, no real accounts, nothing moves in the real world; a sandbox "transfer" only mutates the seed. Sandbox results are for testing and demonstration and are not financial records.

Sandbox access does not create access to the live service. Live access, where offered, is subject to the applicable agreement and to identification, verification and due diligence requirements under the satchel.eu terms. Joining the waitlist is not an account application. Supporting documents may be requested.

The rails underneath

The live API is operated by Satchelpay UAB (reg. No. 304628112, Upės St. 21-1, LT-08128 Vilnius, Lithuania), holder of electronic money institution licence No. 28 issued by the Bank of Lithuania. Client funds in the regulated e-money service are safeguarded in accordance with applicable requirements. Electronic money is not a deposit and is not covered by the Lithuanian deposit guarantee scheme. This page covers the MCP connector and this site; for information about the regulated e-money service, see satchel.eu/security.

Responsible disclosure

Found a vulnerability — in the connector, the sandbox, or this site? Write to support@satchel.eu with steps to reproduce. We review reports. Please don't test against live systems or other people's data; the sandbox exists precisely so you don't have to.