Hash a file in this browser. Bytes never leave the device. Paste the digest into sample.html or your MCP client.
+ +Waiting for a file…+ + + diff --git a/site/index.html b/site/index.html index 4e3724d..a894b4e 100644 --- a/site/index.html +++ b/site/index.html @@ -4,7 +4,7 @@
Model Context Protocol
-Register once. The token stays in a private file on your machine, or in your assistant’s own login store. It does not go in the chat, and it does not go in the client config.
+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.
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…
+ + + +| Target | File | Size | SHA-256 |
|---|
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
# 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
+ This is the install for a person or a server you control. uv runs the command. You do not clone this repository.
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
https://api.veraetime.net.600 and prints your username, role, and expiry. It does not print the token.uvx verae-mcp-timestamping-server session.600. It does not print the token.uvx verae-mcp-timestamping-server session.If you start the server before registering, it prints those same steps on its error stream and still starts. Global stamps need the file. Local stamps do not.
-Pick the environment you use. The config names the program. It does not contain the token.
Claude Desktop
macOS file: ~/Library/Application Support/Claude/claude_desktop_config.json. Windows file: %APPDATA%\Claude\claude_desktop_config.json. Restart Claude after saving.
+macOS: ~/Library/Application Support/Claude/claude_desktop_config.json. Windows: %APPDATA%\Claude\claude_desktop_config.json.
Cursor
User file: ~/.cursor/mcp.json. A project file is .cursor/mcp.json in that project. Restart Cursor after saving.
+User file: ~/.cursor/mcp.json. Project file: .cursor/mcp.json.
VS Code and others
-The same JSON works for any client that reads the Model Context Protocol mcpServers map, including VS Code with an MCP extension.
Local uvx
+Use command: uvx / args: ["verae-mcp-timestamping-server"] instead of a remote URL when you want the process on your machine.
The assistant starts the server. Your login in ~/.verae/auth.properties is the one it uses.
-{
- "mcpServers": {
- "verae-timestamping": {
- "command": "uvx",
- "args": ["verae-mcp-timestamping-server"]
- }
- }
-}
- No local program. The assistant connects to this host. When per-user sign-in is on, the first connection opens a browser page at /account to create an account or log in. That token stays in the assistant’s OAuth store, not in this file.
-{
- "mcpServers": {
- "verae-timestamping": {
- "url": "https://mcp.veraetime.net/mcp"
- }
- }
-}
Your machine
Mode 600, owned by you. Holds the JWT, its expiry, your username, and your password so a stamp can log in again before the 24-hour token expires. Do not commit this file.
+Mode 600. Holds the JWT for local/global stamps. Do not commit this file.
Your assistant
-A browser login on the public server gives the assistant a VeraeTime JWT and a refresh token. The Python client stores that under ~/.verae/oauth/mcp-tokens.json, also mode 600.
+Browser login on the public server keeps tokens in the assistant’s OAuth store, not in mcp.json.
Never
Do not paste the token into a conversation or into the client config. session shows the username and expiry if you need to confirm the login.
Do not paste tokens into a conversation or client config.