Ordinary MCP routers
They terminate OAuth and rate limits, then forward the raw customer record into the model once the call is allowed.
Product
Solutions
Free Tools
Reverse Proxy MCP Gateway · JSON-RPC
Maskio sits between MCP clients and the servers you already run. Tool reads are masked. Tool writes are restored in flight. A read-only policy can refuse destructive calls before they reach Postgres.
Streamable HTTP · Claude Desktop · Cursor · Windsurf · n8n
01
Agent calls get_customer through mcp.maskio.io.
02
The CRM row is tokenized in RAM before the model sees it.
03
update_deal comes back with [EMAIL_1] and is restored at the edge.
04
delete_contact or DROP TABLE stops when the policy says so.
They terminate OAuth and rate limits, then forward the raw customer record into the model once the call is allowed.
Stars and [REDACTED] blocks remove the identifier the next tool needs. The invoice or CRM update fails.
[PERSON_1] and [IBAN_1] stay stable for the session and are resolved only on the upstream hop.
This inspector runs locally. The production gateway applies the same idea on the EU cluster with your real upstream.
What the model receives
{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "get_customer",
"arguments": { "email": "[EMAIL_1]", "nif": "[NIF_1]" }
}
}{
"mcpServers": {
"crm-protected": {
"url": "https://mcp.maskio.io/v1/mcp/gateway/gw_live_98a7f6",
"headers": { "Authorization": "Bearer mp_live_..." }
}
}
}The gateway accepts Streamable HTTP (POST, GET, and DELETE) on /v1/mcp/gateway/{id}. The native server also exposes legacy SSE at /v1/mcp/sse for older clients.
The dictionary stays in RAM for the workspace TTL: 15 minutes on Free, 1 hour on Builder, 24 hours on Team, and up to 7 days for MCP tokens on Agency.
Yes. Register each upstream separately. Tokens are scoped to the workspace, so a person token from Postgres can be restored on a later HubSpot call in the same session.
The free plan includes 1,000 bidirectional MCP calls a month.