Verae

Same MCP · many clients

Ways to use Verae timestamps

Hash locally; stamp digests only against the public Streamable HTTP endpoint. Start with AI MCP, then choose a browser, Mac/Windows UI, CLI, JS, or curl client. File bytes never upload.


3 · UI · Windows

Windows GUI

Frozen amd64 EXEs — PySide6 GUI, CLI, optional hasher. SmartScreen warns (not code-signed); verify SHA-256 first.

4 · CLI

Command line

Official Python client: hash locally, stamp via MCP, write receipts under ~/.verae/receipts/. On Windows use verae-timestamp.exe.

uvx verae-mcp-timestamping-client \
  --url https://mcp.verae.ai/mcp \
  --scope global \
  ./document.pdf

5 · JavaScript

Embed with fetch

Any web app: WASM/WebCrypto hash in-page, then POST Streamable HTTP JSON-RPC to /mcp (CORS *). Session id from Mcp-Session-Id.

6 · curl

Raw JSON-RPC

initialize → notifications/initialized → tools/call (stamp, verify, hash_report). Include Accept: application/json, text/event-stream.

Also

Local hasher · uvx server

Download verae-sha256 for your OS, or hash in-browser with WASM. Optional local MCP: uvx verae-mcp-timestamping-server and … setup for machine login.

Downloads hub

Stable artifact URLs on this host. macOS zip is Developer ID + notarized (not MAS).

macOS direct download (no TestFlight)

Universal Verae Timestamping.app (v0.2.1 / build 7), signed Developer ID Application: FlightLookup Inc. and Apple-notarized with staple. Gatekeeper accepts as Notarized Developer ID.

  1. Download VeraeTimestamping-macos-universal.zip (~546 KiB).
  2. Unzip → drag the app to /Applications (optional).
  3. If Gatekeeper still blocks a quarantined copy: right-click → Open, or run xattr -dr com.apple.quarantine "/Applications/Verae Timestamping.app".
  4. Open → first launch (MCP default https://mcp.verae.ai/mcp).

CLI without the .app: uv sync then uv run verae-timestamp … in the client repo, or uvx verae-mcp-timestamping-client when published.

Request a macOS TestFlight invite

Optional App Store–style beta. Prefer the direct notarized zip if you do not want TestFlight. External testing still requires Apple Beta App Review — until that lands, invites are added manually for your Apple ID.

Public join link

When external Beta Review is approved, open:

https://testflight.apple.com/join/dsHsyx2Z

If the link says the beta is full or unavailable, request an invite below.

Request invite (Apple ID email)

Submit the Apple ID email you use for TestFlight. The server adds you to the external testers group via App Store Connect and resends the invitation.

Fallback: email marchon@gmail.com

Enrollment can succeed while the build is still WAITING_FOR_BETA_REVIEW — you may not see the app in TestFlight until Apple approves the beta.