MCP server · Developer tools
OpenTTT Proof-of-Time MCP server
Give your AI a tamper-proof timestamp for each step it takes, so it can remember its work after a long chat.
This is a small helper that lets your AI stamp each step of a long task with a signed, verifiable timestamp, stored outside the chat. It is handy if you run long jobs with an AI assistant and notice it forgets what it already did. Think of it as a receipt book your AI can write to and read back later.
What is an MCP server? The 30-second version
On its own, your AI can only chat with you inside one conversation. An MCP server is a small helper program you connect to your AI that gives it a new skill or a link to another service. This one links your AI to a timestamp service called OpenTTT, which signs and stores a record every time your AI says "this step happened now". Once connected, your AI can write those records and look them up again later, even in a brand new chat.
What this MCP server does
You ask your AI to do a long task, like refactoring code across many steps. As it works, it calls this helper to stamp each step with a name and a signed timestamp. The helper sends that stamp to an outside server, which keeps the record safe and separate from your chat. Later, even after the chat has been trimmed down, you can ask your AI what it did in a given step, and it looks the record up by name. You get back the exact time, the order of steps, and proof that the record was not changed.
Click to zoomWhat you can do with it
- Stamp each step of a long task with a signed timestamp
- Look up a past step by its name and get the exact record back
- Walk backward and forward through the chain of steps your AI took
- Verify that a timestamp record is genuine and unchanged
- Roll up many steps into a short summary before the chat gets too long
- Check the health and stats of the timestamp server
Try asking your AI
- “Stamp this step as refactor-auth-step1”
- “What did I do in refactor-auth-step1?”
- “Show me the chain of steps leading up to step-2, five levels back”
- “Make a checkpoint of everything from the last hour so I do not lose it”
What it gives back to you
You get back a short record with the step name, the time it was stamped, a link to the previous step, and a signed hash you can verify. When you ask for a chain, you get a list of ancestor steps in order, plus any steps that came after. Checkpoints give you a compressed summary you can read at a glance. Everything shows up as plain text in the chat.
Before you start
What you need
- The Claude desktop app or Claude Code (or another tool that supports MCP servers)
- Node.js installed on your computer so the npx command can run
- An OpenTTT API key if you want more than the free 100 calls per day (optional)
Good to know
The records are signed and hard to change once written, so be careful with the step names you use and do not stamp anything you would not want kept on an outside server.
Install it with your AI
Add OpenTTT Proof-of-Time MCP server to your AI, no technical skills needed
You don't install anything by hand. You copy one prompt, paste it into an AI that can work on your computer, and it checks, installs and connects the server for you, asking you when it needs something.
Sign in to get the install prompt
Members get a ready-made prompt that lets the Claude desktop app check OpenTTT Proof-of-Time MCP server, install it and connect it for them, step by step. You don't need any technical skills: you copy, paste and answer a few questions. Your connected AI can also find and install any of the 4,066 MCP servers here for you.
Who it's for
People running long, multi-step AI workflows, like developers using Claude Code on big codebases, who need the AI to remember what it already did.
