Portable memory · Personal profile · Connected sources
φαντάζειν — to make visible. Your own context, made visible to every AI you use — not locked inside one of them.
MultiPass hosts your memory, profile, and connected sources — Notion, email, tasks — in a container that is yours alone. Paste one URL into any MCP-enabled AI. Every LLM. Every device.
isolated container per customer · full export, anytime · open protocol — no lock-in
How it works
A container spins up for you — yours alone, isolated from every other customer. You get one URL.
Notion, email, tasks, calendar. Each one a connector you can revoke as easily as you added it.
Into Claude, ChatGPT, Cursor, a local model. One OAuth screen later, it knows you. All of them do.
The problem
Today
With MultiPass
The sensitive vault
Health. Legal. Family. Residency. These live in a separate vault — encrypted apart from the rest of your context, with consent granted per category, per client.
When an AI connects, you see exactly what it asks for — and exactly what it doesn't get. A coding assistant has no business knowing your medical history. So it doesn't.
Vault categories: health · legal · family · residency
Consent: per category, per client · revocable anytime
multipass.host/consent
Claude wants to connect
Pricing
Portable memory + profile. Take your context to any AI.
per person · VAT excl.
Your whole digital life — sources, memory, and the vault.
per person · VAT excl.
Everything connected. First in line for what's next.
per person · VAT excl.
Extra connectors, €2/mo each — on any plan. Upgrade, downgrade, cancel anytime. Full export included on every tier, always.
Open protocol
MultiPass is the managed way to run HCS — the open Hosted Context Server protocol. The spec, the server, the export format: all public. If I ever raise prices, degrade the service, or disappear, you take your export and self-host the same thing. That exit is the reason to trust the paid version.
MIT licence · self-host docs included · export = a directory of files you can read
Questions
Exactly what the consent screen shows: the scopes you grant, nothing else. Memory and profile by default; connected sources if you allow them; vault categories only if you grant each one explicitly. You can revoke any scope, for any client, at any time.
Hosted Context Server — an open protocol for serving personal context over MCP. The spec and reference server are public and MIT-licensed. MultiPass is a managed HCS host; anything it does, you can self-host.
Yes. One click produces a complete archive — memory, profile, vault, connector configuration — in the open HCS export format: a directory of files you can read, and that any HCS server can import. No proprietary blobs.
In a container provisioned for you alone, in the EU. No shared databases, no pooled indexes. Vault categories are encrypted separately from the rest of your context.
Anything that speaks MCP: Claude, ChatGPT, Cursor, and local models through an MCP client. You paste your URL, pass one OAuth screen, and the tool has your context.
Export first — it's one click and always available. After cancellation your container is kept encrypted for 30 days, then destroyed. Or skip the wait: take your export and self-host HCS the same day.