verae-mcp-timestamping-server/README.md

verae-mcp-timestamping-server

Verae MCP timestamping server. Hash-only stamps via leaf locald/NATS.

The MCP process never hashes content. Clients send a SHA-256 hex digest. scope=local writes ~/.verae/mcp-timestamp-local.json. scope=global POSTs to https://api.veraetime.net/api/timestamp (same wire as verae-timestamp/global.Client). want_scope=global verifies against that API as the central source of truth. Bearer token: VERAE_GLOBAL_TOKEN or ~/.verae/auth.properties.

Install

cd /Users/marchon/research/modelcontextprotocol/verae-mcp-timestamping-server
uv sync --group dev

Usage

Inspector (stdio, memory ledger):

uv run mcp dev src/verae_mcp_timestamping_server/server.py

Streamable HTTP (http://127.0.0.1:8000/mcp):

VERAE_MCP_TRANSPORT=streamable-http uv run verae-mcp-timestamping-server

Tests:

uv run pytest

HTTP stamp traces (HTML viewer) live under debug-trace/<YYYY-MM-DDTHHMMSSZ>-<slug>/:

uv run python scripts/transaction_log_test.py
open debug-trace/2026-09-20T143541Z-verae-debug-test/transaction-log-test.html

Global stamp (central VeraeTime). Token lives at ~/.verae/auth.properties (mode 600):

# refresh: POST https://api.veraetime.net/auth/login → access_token=
# or: export VERAE_GLOBAL_TOKEN=...
# then stamp with scope=global

Do not send file bytes to stamp. Local receipts persist at ~/.verae/mcp-timestamp-local.json (VERAE_LEDGER_PATH).

Contributing

Questions: this research workspace. PRs welcome. Protocol questions belong at https://github.com/modelcontextprotocol. Timestamp ledger questions belong with verae-timestamp / locald.

License

UNLICENSED © George Lambert