Coverage and implementation status
A control appears only when ShareLess can pause the request or hold the information. This page shows what is available now, what is coming next, and what is not covered.
ShareLess can compute a bounded spending answer on your iPhone, apply your release choices, and pause before the result reaches a connected AI. Raw statements, individual transactions, and account numbers stay on the phone.
A business we have onboarded can open a setup request, your AI can read it and propose items, and you approve them in the iPhone app. Both ends are gated: business keys are installed by an operator rather than issued by a form, and approving needs the iPhone app, which is on invite-only TestFlight. Android cannot approve a connection.
A connection release is stored on ShareLess servers so the business can pull it, and the items pass through the AI you chose. That is a different model from the on-device vault, and we do not describe it as staying on your phone.
Every grant you approve is listed on your account page and in the app, and you can revoke any of them. Revoking records the revocation and reports it to the business the next time it pulls the session. It does not retrieve the copy the business already holds, and ShareLess holds no credential of theirs to withdraw. Their own systems are where their access ends.
The middle of our spine: a business declaring the least it will accept, and your side answering there rather than at the maximum, so that a routing and account number can satisfy an ask that would otherwise take a whole statement. There is no code behind this. You can switch proposed items off before approving, and on an item you keep, any content class the business flagged stays off until you turn it on. What has no code behind it is the other direction: answering an ask with a smaller artifact of the same fact.
The approval sheet groups an ask under the categories a business declares, including the things it promises never to ask for. The server now sends that grouping where the app reads it, and the app can render it, so what remains is distribution: the grouping landed after the build currently out with pilot testers, and it appears once your app updates. Until then the sheet falls back to a flat list, which is complete and accurate but not grouped.
A connected AI can request one exact saved field for a stated reason. ShareLess checks the rule independently and the phone decides whether a value held by ShareLess leaves. The AI does not have the value beforehand.
A custom attention threshold can add scrutiny to the limited ShareLess-run checkout path. It is not a universal spend cap and does not cover purchases made in another app or browser. Payment authority remains with the wallet, issuer, processor, or merchant.
The exact-email contract, phone review, and device-confirmation foundation exist. Gmail account connection, AI submission, phone execution, and provider receipts are not available yet, so Gmail does not appear as an active app control.
Social controls stay hidden until ShareLess can connect the exact destination account and execute only the approved post. Personal Instagram, WhatsApp, iMessage, and LinkedIn messages are not covered today.
Add ShareLess as a custom connector. Exact field requests and the existing vault tool surface are live now: the request reaches your phone, and only an approved value is returned. Use this connector URL:
https://app.shareless.ai/api/mcp/remote
On this remote path, ShareLess opens an approved value in memory long enough to pass it to your AI and does not store that plaintext. While a request is waiting on your phone, the key that opens its answer is held on our server, encrypted at rest, for the life of that request (about three minutes); it is cleared when the request is answered or lapses. This path is not server-blind. For a path where ShareLess cannot open the value, use the local Claude Desktop bundle below.
Follow your MCP client's current custom-connector setup. Access can depend on the client, workspace plan, and administrator permissions.
Connecting the MCP endpoint does not by itself let ShareLess stop a post, email, or message performed through some other tool. General-purpose protected-action send and post tools are not available yet.
Install the ShareLess Vault bundle. It runs on your own machine and opens approved values locally, so ShareLess relays only ciphertext it cannot read. Once Claude uses a value, it still reaches Anthropic like any other message. The local bundle protects the field-release path; it does not turn outside account actions into enforced ShareLess actions.
The shared contract binds the authenticated AI connection, action class, exact recipient, source or destination account, exact text, document, field list or amount, the boundary that fired, server-computed flags, enforcement label, and expiry. A deterministic payload hash changes when any reviewed fact changes. The contract validates the review facts; it does not itself execute an action or mint authority.
The current protected-action foundation is intentionally narrow and includes exact Gmail email fields. It is not a general-purpose API for sending email, messages, or posts, and it grants no authority until a real executor consumes the approved action.
Make Private, Fingerprint, and opt-in local vault fill run on your device. The extension is open-source under Apache-2.0. Local fill can keep ShareLess blind to a value, but the extension is not a connected-account broker and cannot promise to intercept every AI action on a website.
Chrome Web Store listing coming soon.
Active boundaries and approval sheets live on iPhone. Connect an AI, review exact field and money-information requests today, and see new controls only after a destination path works end to end.
Android is in the same pilot as iOS, but it is not the public install path yet. Use iPhone until a Play listing is available.
MCP tool discovery is the source of truth for the live endpoint. The stable data-control surface currently includes:
vault_list_fields and vault_get_field, list metadata and request one exact fieldvault_list_packs and vault_get_pack, list and request a grouped set of fieldsvault_request_intent, resolve the minimum field set for a stated taskvault_add_context, propose low-sensitivity context; the phone confirms before anything is writtenfinance_catalog, finance_query, and finance_result, compute a bounded answer on device before releaseExisting checkout, device-handoff, and session tools remain in discovery during the wallet-handoff migration. They are transition interfaces, not the new product promise. No MCP tool should be described as an enforced send or post until a connected-account executor actually performs it.