VaultProof

VaultProof MCP

Give ChatGPT useful context—not your provider keys.

VaultProof's remote MCP server lets ChatGPT review non-secret credential metadata and explain where VaultProof belongs in your backend. It never returns raw credentials, scans repositories, modifies code, or executes provider requests.

Connect ChatGPT Manage connections
Public contract
  1. 1Two narrowly scoped, read-only tools.
  2. 2OAuth authorization code flow with PKCE S256.
  3. 3Only credential label, provider, and project metadata.
  4. 4Revocable access with short-lived scoped tokens.

Capabilities

Useful account context with a deliberately small surface.

The public MCP contract is limited to two jobs: showing which protected credential entries exist and explaining how VaultProof should be placed at the server-side provider boundary.

Protected inventory

Review the credential labels, provider names, and project names already available to the authenticated VaultProof account.

vaultproof.credentials.list

Placement guidance

Get provider-aware recommendations for compatible proxy routing or runtime-only secret injection at the server-side provider boundary.

vaultproof.integration.guide

Least-privilege OAuth

Connect through an authorization-code flow with PKCE S256, explicit consent, narrow read scopes, and short-lived access tokens.

credentials:metadata:read
capabilities:read

Revocable connections

Review each approved MCP client and revoke its grant. Refresh tokens rotate with reuse detection, and revocation blocks current access and future refreshes.

Review · revoke · reconnect

Minimized output

Tool responses exclude raw credentials, token values, internal IDs, timestamps, request IDs, diagnostics, source files, mutations, and provider execution.

Read-only · non-destructive
Intentionally not included The MCP has no scanner, file reader, source-code input, secret retrieval, mutation, provider execution, checkout, purchase, or upgrade tool. Never paste a credential into ChatGPT or an MCP argument.

Connect ChatGPT

Add the production HTTPS endpoint in Developer Mode.

VaultProof supports existing accounts through OAuth. ChatGPT opens the VaultProof sign-in and consent flow when authorization is required.

Remote MCP server URL
https://mcp.vaultproof.dev/mcp
  1. 1

    Enable Developer Mode

    In ChatGPT, open Settings → Security and login, then turn on Developer mode. Availability can depend on your account or workspace policy.

  2. 2

    Add the server

    Open ChatGPT Plugins, select the plus button, and create a developer-mode connection using the full URL above, including /mcp.

  3. 3

    Review OAuth consent

    Sign in to the intended VaultProof account, review the requested read-only scopes, and approve only if the client identity and permissions are correct.

  4. 4

    Start a new chat

    Add VaultProof from the tools menu, then use one of the example prompts below. If the connection metadata changes, refresh it from the Plugins page before retesting.

Existing accounts only The ChatGPT connection does not create accounts, show subscription plans, start trials, collect cards, or initiate checkout. Account creation and billing remain separate VaultProof website workflows.

Tool contract

Two tools, both read-only and non-destructive.

Tool schemas and server instructions keep outputs minimized and prevent future implementation changes from silently broadening the public surface.

Tool What it returns OAuth scope
vaultproof.credentials.list Credential label, provider, and project name only. credentials:metadata:read
vaultproof.integration.guide Server-side placement, safe setup commands, and provider protection mode guidance. capabilities:read

Security boundary

Authorization is explicit, scoped, short-lived, and revocable.

The MCP endpoint authenticates the client and user before reaching credential metadata through a private Cloudflare service binding.

OAuth + PKCE

Authorization codes use PKCE S256, validated client metadata, issuer-bound responses, and explicit consent.

Minimized output

Raw keys, token values, internal IDs, project IDs, timestamps, request IDs, and diagnostics are removed from tool responses.

Revocation controls

Refresh tokens rotate with reuse detection. Revoking a grant blocks existing access tokens and future refreshes.

Placement rule Your backend application calls VaultProof at the outbound provider-client boundary. Raw credentials never belong in browser code, source control, prompts, or MCP arguments.

Example prompts

Ask for inventory context or server-side placement.

These prompts stay within the current public contract and are suitable for confirming tool selection after connection.

Try in a new ChatGPT conversation
List the protected credential metadata in my VaultProof account.

Which providers and projects have protected credentials configured?

Tell me where VaultProof belongs for my protected providers.

Manage access

Review or revoke every connected MCP application.

Use the account connection page to inspect the approved client and scopes. Revocation immediately blocks the grant's current access tokens and future refreshes; reconnecting requires a new OAuth approval.

Manage MCP connections MCP support