Helm-Protocol/openttt-mcp

> Reference implementation of draft-helmprotocol-tttps (IETF Experimental)
**Proof-of-Time attestation — Ed25519-signed timestamps with multi-source corroboration and explicit error bounds. IETF draft-helmprotocol-tttps**
---
EU AI Act Art. 50 — AI-Generated Content Transparency
TTTPS provides cryptographic time-provenance for AI-generated content at the moment of creation. A pot_generate call anchors a tamper-evident timestamp to a cryptographic hash of the content record — independently of any embedded metadata.
**C2PA complementarity**: C2PA metadata is stripped during recapture, transcoding, and format conversion. TTTPS survives as an external anchor independently verifiable without metadata chain continuity — allowing forensic reconstruction of content provenance even when embedded markers are absent.
**GDPR-compatible by design**: PoT records contain no content and no personal identifiers. Each record binds a cryptographic hash (SHA-256 + HMAC-SHA256) to a multi-source time attestation. No plaintext content transits or is stored on Helm servers.
IETF specification: draft-helmprotocol-tttps (ISE track). Contact: peter@kenosian.com.
---
The Problem: Workflow Amnesia
Every Claude Code long-horizon workflow hits the same wall: **context compression erases action history.**
Agent B has no memory of what Agent A decided. Agent A resumes after compression with no record of its own prior steps. Duplicate work. Lost decisions. State corruption.
**ttt-mcp is the external causal chain that survives context compression.**
Every workflow step is anchored to a cryptographic timestamp on an **external server** — physically separate from Claude's context window. When compression happens, agents call pot_query(eventId) for O(1) exact step recall and resume with full causal context.
---
Mathematical Guarantees
| Layer | Mechanism | Guarantee |
|-------|-----------|-----------|
| **Identity** | SHA-3 eventId (256-bit) | Collision probability 2⁻²⁵⁶ — practically zero |
| **Lookup** | O(1) exact retrieval | No context consumed by history reconstruction |
| **Ordering** | TTTPS causal timestamps | Total order on events — tamper-proof sequence proof |
| **Causal chain** | prevEventId DAG | O(depth) traversal — depth ~100 for 1B-token workflows |
| **Non-repudiation** | Ed25519 signature | Cryptographic proof of who acted when |
| **Resilience** | Erasure-coded cryptographic shards | ≥97% recovery at BER=0.05, 99.88% at BER=0.02 (theoretical) |
| **Persistence** | Redis AOF + 90-day TTL | Server survives context compression and restarts |
---
Quick Start
Claude Code
With an API key (raises the free limit to your plan's monthly quota):
Claude Desktop
Add to claude_desktop_config.json:
Cursor
One-click install, or add the same mcpServers block above to .cursor/mcp.json.
Free tier: 100 calls/day per IP — no signup needed.
---
5-Minute Test
Once connected, run this sequence in Claude:
**Step 1 — Stamp a workflow step:**
Just tell Claude naturally:
> "Stamp this step as my-first-step"
> "Record what I just did as refactor-auth-step1"
Claude calls pot_generate automatically. Or call it directly:
**Step 2 — Simulate context compression:** start a new Claude session
**Step 3 — Recover in the new session:**
Tell Claude:
> "What did I do in my-first-step?"
> "Recover my last workflow state"
Or call directly:
→ Returns exact record. Amnesia gone.
**Step 4 — Build a causal chain:**
→ Full backward chain. Cryptographically ordered.
---
10 Tools
| Tool | Purpose |
|------|---------|
| pot_generate | Stamp a workflow step with a cryptographic timestamp |
| pot_verify | Verify a PoT signature |
| pot_generate_v2 | Generate the draft-11 180-octet PoT Record v2 core (canonical wire profile) |
| pot_verify_v2 | Verify a v2 record; optional TLS 1.3 exporter binding proof (fails closed without TLS) |
| pot_verify_v08 | Verify a draft-08 §3 Payload Digest record |
| pot_query | O(1) exact lookup by eventId — core amnesia recovery |
| pot_graph | Traverse causal DAG (backward + forward chain) |
| pot_checkpoint | Roll up events into a compressed summary — use every ~100 events or before long tasks |
| pot_stats | Server statistics and mode status |
| pot_health | Health check |
---
Tool Parameters
pot_generate
Stamp a workflow step with a cryptographic timestamp. For Claude Code: use eventId + prevEventId. For DeFi: use txHash + chainId + poolAddress. To bind the attestation to a specific piece of content (draft-08 §3 Payload Digest), also supply contentDigest. One of eventId, txHash, or contentDigest is required.