Model Context Protocol

Hash locally. Stamp remotely.

Download a small verae-sha256 binary for your OS (or use WASM on mobile/browser). Digests go to the MCP server. File bytes stay on your machine.

Get the local hasher

No repo clone. This page detects your platform, fetches the matching published binary from /hasher/, and falls back to WASM/JS when a native build is not available.

Detecting platform…

All published binaries

Target	File	Size	SHA-256

Manifest: /hasher/latest.json · Source rebuild: ./scripts/publish-hasher.sh in the client repo.

Connect an MCP client

Point Claude, Cursor, or another MCP client at this host. You do not need to run a local server.

{
  "mcpServers": {
    "verae-timestamping": {
      "url": "https://HOST/mcp"
    }
  }
}

Public endpoints: https://HOST/mcp · also mcp.veraetime.net/mcp · mcp.georgelambert.org/mcp

Hash a file, then stamp

# after installing the binary as verae-sha256 on your PATH:
DIGEST=$(verae-sha256 ./document.pdf)
echo "$DIGEST"
# then ask your MCP client to call tool "stamp" with { "sha256": "$DIGEST", "scope": "global" }
# or try the browser sample:
#   open sample.html and paste the digest

Optional: register on your machine

For a local uvx server (or global stamps that need a VeraeTime account), register once. You still do not clone a repository.

uvx verae-mcp-timestamping-server setup

Choose new to create a VeraeTime account, or existing to log in.
It writes ~/.verae/auth.properties with mode 600. It does not print the token.
Check later with uvx verae-mcp-timestamping-server session.

Claude Desktop

macOS and Windows

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json. Windows: %APPDATA%\Claude\claude_desktop_config.json.

Cursor

Project or user

User file: ~/.cursor/mcp.json. Project file: .cursor/mcp.json.

Local uvx

Run on this computer

Use command: uvx / args: ["verae-mcp-timestamping-server"] instead of a remote URL when you want the process on your machine.

Where credentials live

Your machine

~/.verae/auth.properties

Mode 600. Holds the JWT for local/global stamps. Do not commit this file.

Your assistant

OAuth store

Browser login on the public server keeps tokens in the assistant’s OAuth store, not in mcp.json.

Never

Chat or mcp.json

Do not paste tokens into a conversation or client config.