Verae

Model Context Protocol

Install Verae timestamping.

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.

Register on your machine

This is the install for a person or a server you control. uv runs the command. You do not clone this repository.

uvx verae-mcp-timestamping-server setup
  1. Choose new to create a VeraeTime account, or existing to log in.
  2. Enter a username and password. The command calls https://api.veraetime.net.
  3. It writes ~/.verae/auth.properties with mode 600 and prints your username, role, and expiry. It does not print the token.
  4. Check it later with 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.

Connect an assistant

Pick the environment you use. The config names the program. It does not contain the token.

Claude Desktop

macOS and Windows

macOS file: ~/Library/Application Support/Claude/claude_desktop_config.json. Windows file: %APPDATA%\Claude\claude_desktop_config.json. Restart Claude after saving.

Cursor

Project or user

User file: ~/.cursor/mcp.json. A project file is .cursor/mcp.json in that project. Restart Cursor after saving.

VS Code and others

mcp.json

The same JSON works for any client that reads the Model Context Protocol mcpServers map, including VS Code with an MCP extension.

Run it on your computer

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"]
    }
  }
}

Use the public 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"
    }
  }
}

Where the token lives

Your machine

~/.verae/auth.properties

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.

Your assistant

OAuth file

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.

Never

Chat or mcp.json

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.