OpenTTT Proof of Time MCP Server
@Helm-Protocol
Basic information
About OpenTTT Proof of Time MCP Server
Cryptographic transaction ordering verification for AI agents. Multi-source HTTPS time │
OpenTTT Proof of Time MCP Server config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"openttt": {
"command": "npx",
"args": [
"-y",
"@helm-protocol/ttt-mcp"
]
}
}
}OpenTTT Proof of Time MCP Server tools
8Generate 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 §3 record binding this attestation to a specific piece of content, also supply contentDigest. One of eventId, txHash, or contentDigest is required.
Verify a Proof of Time using its hash and integrity shards. Returns validity, mode (turbo/full), and timestamp.
Verify a draft-helmprotocol-tttps-08 §3 Proof-of-Time record (as produced by pot_generate's potRecordV08 field): recomputes the Commitment and checks the Ed25519 signature, and — if content is supplied — recomputes SHA-256(content) and checks it against the record's Payload Digest field.
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.
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.
Get PoT statistics: total swaps, turbo/full counts, and turbo ratio for a given period.
Check PoT system health: time source status, subgraph sync, server uptime, and current mode.
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).
Overview
What is OpenTTT Proof of Time?
OpenTTT Proof of Time is a server that provides cryptographic transaction ordering verification for AI agents. It synthesizes time from multiple HTTPS sources (NIST, Google, Cloudflare, Apple) and combines an integrity pipeline (GRG) with Ed25519 signing to produce verifiable proof-of-time stamps.
How to use OpenTTT Proof of Time?
The server offers five tools: pot_generate, pot_verify, pot_query, pot_stats, and pot_health. Invoke these through an MCP client to create, verify, or query time proofs; fetch statistics; or check server health.
Key features of OpenTTT Proof of Time
- Multi-source HTTPS time
More Productivity MCP servers

crosscode-cli
amsultan2010Multiplayer coding in the agentic era through an MCP server for real-time codebase sync between your agents.

QuipAssist
Copliancy IncEquipment, repair and maintenance records for multi-location operators: assets, work orders, preventive maintenance, parts and vendors. Agent changes wait as drafts for review.

Genviral
GenviralPlan, create, schedule, publish, and analyze social media content from AI assistants through Genviral's secure OAuth MCP server.

PaperOffice AI
PaperOfficeBuilt for companies. Ready for AI agents. PaperOffice is the headless DMS your agent can actually operate: one MCP endpoint to search, read, upload, extract and sign business documents — no UI, no glue code. AI-OCR, invo
WhatsMCP
whatsmcpWhatsMCP — WhatsApp for AI agents. Put an AI agent on a real WhatsApp number. Expose regular WhatsApp accounts to your LLM agents over JSON-RPC. A complete Model Context Protocol server that turns phone numbers into addr
Comments