Zkshare MCP Server

Privacy-oriented context API for users, AI agents, and back-office systems. A single HTTP entrypoint (`POST /api/v1/context`) handles **encrypted

Local serverstdioTypeScript

What is the Zkshare MCP Server?

Privacy-oriented context API for users, AI agents, and back-office systems. A single HTTP entrypoint (POST /api/v1/context) handles encrypted fact storage

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Maintainer setup documentation.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
store**Server-sealed:** caller sends value. Server encrypts with AES-256-GCM, computes a salted commitment, generates an embedding (or accepts a 1536-dim embedding), and persists with client_encrypted = false. **Client-sealed
proveLoads a server-sealed fact, decrypts in memory, derives a yes/no answer for the supplied query (LLM with temperature: 0, or a heuristic when external LLMs are disabled), and returns an HMAC-signed proof envelope. Returns
shareSame as prove, plus inserts a row into share_tokens (recipient_agent_id, expiry, proof) and returns a share_token. The token is a 24-byte base64url string, valid for seven days.
searchEmbeds the query, calls match_facts (a security definer SQL function with cosine distance over pgvector), and returns ranked summaries for **server-sealed rows only**. Client-sealed rows are excluded at the SQL level **a
verify_proofValidates an envelope without loading any fact. Malformed envelope returns 400 / VALIDATION_ERROR; well-formed envelope with a bad HMAC returns 200 with data.valid: false.
sandboxExecutes a small allow-listed function inside an isolated node:vm sandbox (no host I/O, 50 ms timeout) and returns the result with attestation metadata and a short-lived HS256 JWT (proof_of_execution). Every response adv

How to install the Zkshare MCP Server

claude mcp add zkshare --env ZKSHARE_API_KEY=your-value --env ZKSHARE_API_URL=your-value --env ZKSHARE_ENCRYPTION_SECRET=your-value --env ZKSHARE_PROOF_SECRET=your-value --env INVALID_API_KEY=your-value --env ZKSHARE_ENCLAVE_JWT_SECRET=your-value --env UPSTASH_REDIS_REST_URL=your-value --env UPSTASH_REDIS_REST_TOKEN=your-value -- npx -y zkshare-mcp

Configuration

VariableDescriptionRequired
ZKSHARE_API_KEYCredential the server authenticates with.Yes
ZKSHARE_API_URLEndpoint or connection string the server talks to.Yes
ZKSHARE_ENCRYPTION_SECRETCredential the server authenticates with.Yes
ZKSHARE_PROOF_SECRETCredential the server authenticates with.Yes
INVALID_API_KEYCredential the server authenticates with.Yes
ZKSHARE_ENCLAVE_JWT_SECRETCredential the server authenticates with.Yes
UPSTASH_REDIS_REST_URLEndpoint or connection string the server talks to.Yes
UPSTASH_REDIS_REST_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • “Use Zkshare to Operation.”
  • “Use Zkshare to store.”
  • “Use Zkshare to prove.”

Frequently asked questions

Privacy-oriented context API for users, AI agents, and back-office systems. A single HTTP entrypoint (`POST /api/v1/context`) handles **encrypted fact storage** Confirm the tools offered by your installed version in the connected client. Tool availability and permissions depend on the server and account configuration.