Openttt Pot MCP server

by Helm-Protocol·io.github.Helm-Protocol/openttt-pot·v0.3.4·1 stars

No reviews yet

Cryptographic audit trail for Claude Code workflows — tamper-proof timestamps, IETF TTTPS compliant.

A91/100grade A

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

A91/100

full report

Adoption

Growing

1 stars104 downloads/wk

Reviews

Write one

Nobody has reviewed Openttt Pot yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Openttt Pot tools (8, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

pot_checkpointwrite action
Create a compressed rollup checkpoint of workflow history. Call this periodically to prevent token explosion when recovering from context compression. Returns checkpointId, compressed event history, chainIntact status, and nextCheckpointHint (recommended events before next checkpoint).
pot_generate
Generate a cryptographic Proof of Time timestamp (draft-helmprotocol-tttps, https://datatracker.ietf.org/doc/draft-helmprotocol-tttps/). For Claude Code workflows: use eventId + prevEventId to build a causal chain. For DeFi: use txHash + chainId + poolAddress. For a spec-conformant draft-08 \xA73 record binding this attestation to a specific piece of content, also supply contentDigest. One of even
pot_graph
Traverse the causal chain of workflow steps. Given an eventId, returns the full backward chain (ancestors via prevEventId) and forward chain (steps that follow). Use after context compression to reconstruct the complete workflow timeline.
pot_health
Check PoT system health: time source status, subgraph sync, server uptime, and current mode.
pot_query
Query Proof of Time records. Use eventId for exact O(1) lookup of a specific workflow step (collision probability 2^-256). Use startTime/endTime for time-range queries.
pot_stats
Get PoT statistics: total swaps, turbo/full counts, and turbo ratio for a given period.
pot_verify
Verify a Proof of Time using its hash and integrity shards. Returns validity, mode (turbo/full), and timestamp.
pot_verify_v08
Verify a draft-helmprotocol-tttps-08 \xA73 Proof-of-Time record (as produced by pot_generate's potRecordV08 field): recomputes the Commitment and checks the Ed25519 signature, and \u2014 if content is supplied \u2014 recomputes SHA-256(content) and checks it against the record's Payload Digest field.

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

no findings

Code scan7 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 23 days ago15/15
Maintainer identityregistry namespace matches repository owner7/10

Overall 91/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How Openttt Pot compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 91/100; higher than 85% of 48,255 servers
Tools: 8; the typical server has 7
Tools that change things: 13%; typical: 0%. Fewer write tools means less an agent can break
GitHub stars: 1; more than 65% of 28,688 servers
Downloads a week: 104; more than 64% of 12,191 servers with a package

What its tools let an agent do: 7 read · 1 change

Install Openttt Pot in Claude Code, Cursor or VS Code

Runs npx -y @helm-protocol/ttt-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add openttt-pot -- npx -y @helm-protocol/ttt-mcp

Add to Cursor

What the publisher says

From the Openttt Pot repository's README, as published. We do not edit it. Read it on GitHub

@helm-protocol/ttt-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.

Claude workflow → [context compressed] → agents call pot_query(eventId)
                                         → external server returns full timeline
                                         → workflow resumes, zero lost state

Mathematical Guarantees

Quick Start

Claude Code

claude mcp add ttt -- npx -y @helm-protocol/ttt-mcp@0.4.0

With an API key (raises the free limit to your plan's monthly quota):

claude mcp add ttt -e TTT_API_KEY=your-key -- npx -y @helm-protocol/ttt-mcp@0.4.0

Claude Desktop

Add to claudedesktopconfig.json:

{
  "mcpServers": {
    "ttt": {
      "command": "npx",
      "args": ["-y", "@helm-protocol/ttt-mcp@0.4.0"],
      "env": { "TTT_API_KEY": "your-key" }
    }
  }
}

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:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Openttt Pot: common questions

Is Openttt Pot MCP server safe?: Yes, by our scan: it is graded A (91/100). Read the Openttt Pot safety report
How do I install Openttt Pot?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Openttt Pot need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Openttt Pot maintained?: The last commit was 24 days ago (2026-10-11). The latest release is v0.3.4.
What can I use instead of Openttt Pot?: Servers from other publishers that do the same job: Tradememory Protocol MCP server and SSH Manager MCP server.
How does Openttt Pot compare with other MCP servers?: safety score 91/100 (higher than 85% of 48,255 servers); tools 8 (the typical server has 7); tools that change things 13% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Openttt Pot

Same job from other publishers: the closest match first, then the best rated.

Tradememory Protocol
Tamper-evident decision audit trail and outcome-weighted memory for AI trading agents.
not reviewed
Established
B
SSH Manager
SSH for AI agents: commands, files, backups and health, with approval, a vault and an audit trail
not reviewed
Established
A