Data access and security
The connector is scoped to the advisor who signed in. Which clients it can read is decided by the identity minted from that sign-in, never by anything the model sends — so no phrasing of a question can widen it.
Who can use it
Two things are checked on every call, and both are properties of the Wealth.com account rather than of the Claude workspace:
- An advisor account. The account must hold the
advisorrole. Client logins and read-only roles are refused. - The
mcpentitlement. Your firm's contract must include Wealth MCP, and the tools you use are further split into read access and write access.
If either is missing the connector still adds and still lists its tools — the refusal arrives when a tool is called, as a sentence telling you to contact Wealth.com. See Troubleshooting.
What it can read
- Clients on the calling advisor's own book, and their profiles, documents, estate structure and tax figures.
- Federal and state tax law for a year, which is about a year rather than about any client.
What it never returns
- A client belonging to another advisor. A client outside the caller's book resolves to nothing on file — the same answer as one that exists nowhere, so the response does not reveal whether the client exists at all.
- Tax identification numbers, Social Security numbers, or an EIN. These are dropped from structured fields and excised from prose.
- Geographic coordinates. A client profile carries the state of residence and no finer location.
- Which advisor a client belongs to. That is on no surface the connector exposes.
These are enforced in one place for every tool rather than per tool, so a tool added later inherits them.
Authentication
Sign-in is OAuth 2.0 against Wealth.com's own identity service at identity.wealth.com. No API keys and no shared secrets are created, and Claude never sees the advisor's password.
The token Claude presents is validated at our edge — signature, algorithm, issuer, audience and expiry — and exchanged for a short-lived internal identity before any client record is read. The token from Claude never reaches a downstream service. Outbound calls carry the minted identity and a correlation id, and nothing else.
Machine-to-machine credentials are refused outright on every tool that touches a client file. Only a signed-in human advisor can reach client data.
Removing the connector in Claude, or revoking the session from the Wealth.com account, ends access. Withdrawing the
mcp entitlement takes effect within a minute. A token already issued stops working within 5 minutes, which is how
long a minted identity is cached. There is no long-lived credential to rotate.
Audit
Every call that touches client information is recorded with the advisor, the client it concerned, the tool, the outcome, and a UTC timestamp — on both settlements, so a refusal is recorded as well as a success. Records are written through an append-only interface and are retrievable by Wealth.com on request.
Only three tools change anything — upload_extract_document, create_shadow_client and promote_shadow_client. The other 15 cannot alter a client file, and none of the 18 deletes a client, a document, or a figure.
Data handling
The server stores nothing. It is a stateless gateway: no database of client data, nothing written to disk, and no client records cached between requests. Every answer is read from a Wealth.com system of record at the time of the call and discarded when the response is sent. The only state the process holds is short-lived and non-client — a minted-identity cache keyed to the caller (5 minutes) and a session handle (15 minutes) — and none of it survives a restart.
Processing stays in Wealth.com's own AWS accounts in the United States. Client data flows between Claude, the server, and Wealth.com's internal services. No client data is used to train any model.
Operational telemetry is separated from client data. Logs, metrics and traces go to Datadog, our monitoring provider, and are built so that request and response bodies never reach them. The compliance audit trail described above is the one record permitted to name a client, and it names them by identifier only.
Redaction runs on every result, by default. A key-matching pass drops fields that must never be returned, at any depth. A second pass reads the prose an upstream author wrote and excises identifying numbers that key matching structurally cannot see. That pass excises rather than refuses, so the advisor keeps the rest of the summary and is told what was removed. Both default to on, so a tool added later is covered by omission rather than by its author remembering.
See the Privacy Policy and the AI Tools Addendum for the full terms.
Limits
| Control | Behavior |
|---|---|
| Per-session client cap | A session opens at most 25 distinct client files. Re-reading a client already touched does not advance the count, and a whole-book read counts as one. It is keyed to the advisor, so rotating a header cannot reset it, and it counts the ask rather than the answer, so probing identifiers is bounded too. Tripping it returns a rate-limited result, not an outage; a new conversation starts a new count. |
| Machine callers | Client-credentials tokens are refused on every client-data tool, and on the resource-read methods, before any tool runs. |
| Request size | JSON-RPC bodies are capped at 4 MB, behind authentication, so an unauthenticated caller cannot force a large parse. |
| Browser origins | Allow-list is empty by default; no browser origin is admitted unless explicitly configured. |
| Identity failures | A failed, refused or timed-out identity exchange is a 403. There is no passthrough mode and no legacy identity to fall back on, so failing open is not a state the process can enter. |
| Transport | TLS only. Port 80 redirects; nothing is served in the clear. |
Troubleshooting
Claude does not show any Wealth.com tools. The connector is connected but not enabled for the conversation. Open the connector menu in the message box and switch Wealth.com on. If it is missing from the directory entirely, your administrator may not have enabled it for the organization yet.
Claude says the assistant is not enabled for your firm. Your Wealth.com account does not carry the mcp entitlement. Contact Wealth.com to have it added — nothing about the Claude side needs changing.
Claude says a tool is limited to advisor accounts. The account you signed in with is not an advisor account. Sign out of Wealth.com and sign in again with your advisor credentials.
Claude says part of your firm's access does not include something. The firm has the connector but not that particular capability — commonly the write tools that file a document or create a client. Everything else on the client file is unaffected.
"List my clients" comes back empty. The connection succeeded but the account has no clients on its book. Confirm you are signed in to the same account — advisors at firms with multiple teams sometimes hold more than one.
Claude says a client is not on file, but you know they are. Households are matched on every name the record holds, so a nickname or maiden name usually resolves. If it does not, the household may be filed under a different surname — try the name as it appears on their most recent return.
Claude says too much has been asked of the client file at once. A conversation can open 25 different client files. That is a guard against bulk extraction rather than a cap on how much work you can do — start a new conversation and the count resets. Whatever has already been gathered is unaffected.
Sign-in opens but never completes. Usually a blocked pop-up or a stale session. Allow pop-ups for Claude, sign out of Wealth.com in the same browser, then connect again. If your organization manages your network, check that mcp.wealth.com and identity.wealth.com are reachable.
An answer says part of the file is unavailable. One service behind that answer could not be reached; the rest of the file is unaffected. Ask again in a few minutes.
Get help
Support runs through Ellie, the Wealth.com assistant. Open the resource center and use the panel there — choose Get Support, or type your question into Ask Ellie a question.
For anything Ellie cannot settle, or anything about a specific client file, email support@wealth.com with the date and time of the conversation and we can trace the exact request.