verae-mcp-timestamping-serv.../README.md
George Lambert 3ec1f0516b
Some checks failed
test-and-deploy / test (push) Failing after 12m55s
test-and-deploy / deploy-138 (push) Has been cancelled
feat(mcp): optional receipt_format on stamp/verify (text/PDF/JSON/MD/CSV/TSV)
Add receipt_format to stamp and verify. Omitted → text; receipt|PDF-Receipt → PDF;
JSON-Receipt → JSON; MD|MD-Receipt; CSV|CSV-Receipt; TSV|TSV-Receipt.

Stamp always returns receipts[] and adds artifacts[] in the chosen format.
Stdio writes ~/.verae/receipts (0600); public MCP returns content_text/content_base64 only.
Verify accepts inline receipt or receipt_path (stdio), parses id, and re-emits an artifact.

Vendors pdfcert (+ slim statuslang, gofpdf) for CERT-01 PDF. Also lands welcome tool
and email-username helpers already wired into register/public paths.
2026-10-20 16:02:20 -04:00

1.7 KiB

verae-mcp-timestamping-server-go

standard-readme compliant

MCP server for digests-only timestamping (public HTTP and local stdio).

Table of Contents

Background

Public writes require caller Bearer (DEC-654). Optional VERAE_MCP_EDGE_URL bills via zap.verae.ai. Account and auth are required for use. On connect, instructions tell the AI to welcome the user and call tool welcome, then signup / login. Only welcome, signup, and login work without a bearer. signup / login return access_token (public HTTP never writes the host credential). Grok: bearer_token_file or local stdio. Job-complete is core NATS only.

Co-contributors: Grok (xAI), George Lambert, Scott "R00tPiG Security" Lindsey — Verae Inc. (verae.com).

Install

go build -o bin/verae-mcp-timestamping-server ./cmd/verae-mcp-timestamping-server

Usage

./bin/verae-mcp-timestamping-server -transport http -addr :8000
# or -transport stdio for laptop host auth

Optional receipt_format on stamp / verify: omit → text; receipt / PDF-Receipt → PDF; JSON-Receipt → JSON; MD / MD-Receipt; CSV / CSV-Receipt; TSV / TSV-Receipt. Stdio writes under ~/.verae/receipts; public MCP returns content_text / content_base64 only.

Contributing

Questions: open an issue on the project Forgejo/GitHub remote, or contact Verae engineering. PRs are accepted when they include tests and do not leak secrets.

License

UNLICENSED © Verae Inc. (verae.com)