---
name: proof-mcp-best-practices
description: Connect to Proof's MCP server to notarize and e-sign PDFs, and to access x401 protected resources with a verified identity. Use a client that follows the latest MCP specification and registers itself with CIMD or DCR, so no client ID or secret is needed.
representative_queries:
  - connect to the Proof MCP server
  - notarize this PDF with Proof
  - e-sign a document with Proof
  - verify my identity with Proof to access a resource
---

# Proof MCP best practices

Proof's MCP server: `https://mcp.proof.com/mcp`

## Client

Agents SHOULD use an MCP Client that follows the latest MCP specification:
[2026-07-28](https://modelcontextprotocol.io/specification/2026-07-28).

## Authorization

There's no API key, client ID or client secret to get from Proof, and nothing for the user to create:
never ask them for one. MCP Clients register themselves, with a
[Client ID Metadata Document](https://www.ietf.org/archive/id/draft-ietf-oauth-client-id-metadata-document-02.html)
(CIMD) or [Dynamic Client Registration](https://www.rfc-editor.org/rfc/rfc7591) (DCR) at the authorization
server's `registration_endpoint`, as a public client (`token_endpoint_auth_method: none`) with PKCE.

## Tools

Agents SHOULD fetch and read the tools' instructions before calling the tools: the server
`instructions` returned at initialization and each tool's description returned by `tools/list`.
They give the context for using each tool.
