MPCVault

• Name: MPCVault
• URL: https://docs.mpcvault.com/
• Category: Institutional MPC wallet infrastructure / wallet control plane / programmable signing platform
• Summary: MPCVault is institutional wallet-ops infrastructure: MPC custody, approval policy, API-driven signing, and treasury workflow in one stack. The wallet label is too small. The real product is the operating surface around who can approve, how machine flows get wired in, and which transaction paths the platform normalizes.
• What it does:
  • Provides multi-chain non-custodial wallets for teams using a 3-of-3 MPC signing model instead of a single private key
  • Splits signing authority across the user device and two separate cloud environments, with docs explicitly describing Google Cloud AMD SEV and Microsoft Azure Intel SGX as part of the trust model
  • Supports vault-level approval policies, quorum controls, key export / recovery paths, and organization or vault member workflows for operational control
  • Exposes REST and gRPC APIs for wallet creation, balances, signing requests, batch payments, and other programmable treasury or operations flows
  • Ships a Dockerized client signer that can receive signing callbacks and automate transaction approval or execution based on backend business logic
  • Extends beyond raw custody into operational tooling such as batch payments, DeFi access, token/NFT handling, cards, and stablecoin off-ramp flows
• Key claims:
  • The overview says MPCVault is a “non-custodial wallet for teams” built on MPC, with all three key shares required for signing and no single party holding complete control
  • The architecture docs specify a 3-of-3 setup across the user device, Google Cloud AMD SEV, and Microsoft Azure Intel SGX
  • The API docs say developers can build automated transactions, deposit-address workflows, batch payments, and message-signing integrations on top of MPCVault’s REST and gRPC interfaces
  • The client-signer docs describe a production-style Docker container that maintains a secure connection, receives signing callbacks, and approves transactions according to application logic
  • The docs index and public proto repo show a broad operational surface spanning architecture, encryption, key export, key refresh, transaction policies, cards, off-ramp, and machine-facing API definitions
• Whitepaper: No classic standalone whitepaper or litepaper was found during this pass. The strongest primary materials were MPCVault’s official docs overview, architecture page, API overview, client-signer guide, docs index, and public API definitions repo; see ../whitepapers/mpcvault-primary-sources-2026-04-26.md.
• Sources:
  • https://docs.mpcvault.com/
  • https://docs.mpcvault.com/llms.txt
  • https://docs.mpcvault.com/architecture.md
  • https://docs.mpcvault.com/api-reference/overview.md
  • https://docs.mpcvault.com/guides/18-how-to-enable-api/client-signer.md
  • https://github.com/mpcvault
  • https://github.com/mpcvault/mpcvaultapis
  • https://raw.githubusercontent.com/mpcvault/mpcvaultapis/main/README.md

Internal linkages

• Strongest comparisons: fireblocks, bitgo, and dfns.

Governance / control risk

• The leverage sits in approval graphs, client-signer deployment, API credentialing, callback handling, policy configuration, and the recovery/export paths around the MPC setup.

• Useful cut: the interesting question is not whether MPCVault is non-custodial. It is how much operational authority still concentrates in the workflow layer wrapped around the shards.

• Last reviewed: 2026-05-27 UTC