Proof-of-Time transaction ordering verification for AI agents. 5 MCP tools.
Reference implementation of draft-helmprotocol-tttps-00 Cryptographic Proof-of-Time for Distributed Systems — TLS-grade time verification without trust assumptions. OpenTTT brings verifiable, Byzantine-fault-tolerant timestamping to any distributed system. Where TLS made HTTP trustworthy, OpenTTT makes ordering and sequencing verifiable. No trust assumptions. No gentleman's agreements. Physics.…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 40 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Reference implementation of draft-helmprotocol-tttps-00 Cryptographic Proof-of-Time for Distributed Systems — TLS-grade time verification without trust assumptions. OpenTTT brings verifiable, Byzantine-fault-tolerant timestamping to any distributed system. Where TLS made HTTP trustworthy, OpenTTT makes ordering and sequencing verifiable. No trust assumptions. No gentleman's agreements. Physics. Current distributed systems rely on trust for ordering: services promise fair sequencing, protocols…
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.