Skip to main content
Three public MCP tools manage encrypted secrets tied to your Proofable Profile. Values are sealed with AES-256-GCM and never returned in plaintext through MCP. Sign in first with OAuth or a Profile access key (Auth). Use the signed-in profile context from proofable_context before create or revoke. When signed in, omit walletAddress. Secrets bind to your profile account from proofable_context.

Create (proofable_secret_create)

List (proofable_secret_list)

Without Bearer auth, the tool returns an empty list and authRequired: true. It does not leak metadata.

Revoke (proofable_secret_revoke)

Requires authenticated ownership of the secret proof. Omit walletAddress when signed in.

Security

  • Never paste secret values into chat logs or public issues.
  • Prefer OAuth or Profile keys in MCP config only. Do not use them in app browser bundles.
  • Rotate or revoke through proofable_secret_revoke and re-create if a value is exposed.

Auth

How MCP sessions authenticate.

Current user

Profile lookup and refresh.
Last modified on September 8, 2026