Architecture overview
Maskio sits between an AI client and the place where personal data actually lives. The model sees stable tokens such as [PERSON_1] and [IBAN_1]. Your CRM, database, or support tool receives the original values only when a write is supposed to happen.
Two MCP modes
The native server at https://mcp.maskio.io/v1/mcp/native gives Claude, Cursor, and similar clients three tools: maskio_sanitize_text, maskio_restore_text, and maskio_sanitize_document. Use it when the human is pasting text or files.
The gateway at https://mcp.maskio.io/v1/mcp/gateway/{id} proxies an MCP server you already run. The agent never learns that server’s URL or credential. Reads are tokenized. Writes are restored in flight.
Both speak Streamable HTTP (POST, GET, DELETE). Send Accept: application/json, text/event-stream.
Sessions
A token only means something inside a session for one organization and workspace. Pass the same session through a multi-step agent. When the TTL ends, or the process restarts, the dictionary is gone. The source record is still in your system.
What is logged
Time, workspace, gateway, latency, and counts such as “2 IBANs”. Not the prompt, not the row, not the resolved token.