
ZKshare
A privacy-first context store that wraps the zkShare HTTP API in MCP tools. Exposes store, prove, share, search, and verify operations over encrypted facts backed by PostgreSQL with pgvector. The server-sealed path lets you encrypt user context server-side and generate HMAC-signed proof envelopes (yes/no answers to queries without exposing the underlying fact). The client-sealed path keeps plaintext out of the operator's reach entirely. Reach for this when you need agents to hold sensitive context across sessions, prove properties of personal data to third parties, or run semantic search over encrypted values. Configure it with your zkShare API key and it proxies everything to the hosted or self-hosted /api/v1/context endpoint.
- tools
- 2
- auth
- Secret needed
- transport
- STDIO
- env vars
- 2
- last updated
- Apr 30, 2026
Tools
2 toolsPublic tool metadata for what this MCP can expose to an agent.
zkshare_storeStores a server-sealed fact via the zkShare API.
Stores a server-sealed fact via the zkShare API.
No parameter schema in public metadata yet.
zkshare_proveDerives a yes/no answer for a stored fact and returns an HMAC-signed proof envelope.
Derives a yes/no answer for a stored fact and returns an HMAC-signed proof envelope.
No parameter schema in public metadata yet.
Sponsors
Configuration
ZKSHARE_API_KEY*secretZKshare API key (zk_live_…). Create one at zkshare.io/api-key — required for POST /api/v1/context.
ZKSHARE_API_URLdefault: https://zkshare.ioAPI origin including scheme; omit for production (https://zkshare.io). Use http://localhost:3000 only when self-hosting.
Readme
zkShare
Privacy-oriented context API for users, AI agents, and back-office systems. A single HTTP entrypoint
(POST /api/v1/context) handles encrypted fact storage, commitment-based proof envelopes,
semantic search over encrypted data, end-to-end-encrypted (client-sealed) facts, and a
isolated sandbox execution for sensitive computations. The implementation is a Next.js
(App Router) application backed by PostgreSQL with pgvector.
This document is for developers integrating against the API and operators self-hosting the service. It is not a marketing brochure — pricing tiers, dashboards, and billing are optional layers defined separately in the application code.
Privacy and security model
The platform is designed around three trust boundaries:
Details
- Repository
- github.com/sp0oby/zkshare
- Website
- zkshare.io/docs
- Category
- Search & Web Crawling
- Package
zkshare-mcp- Transport
- STDIO
- Auth
- Required
- Registry
- MCP registry, active