What it does
The server exposes tools that let an MCP-compatible agent create a SHA-256 hash of a document and stamp it against four public OpenTimestamps calendars. A stamp stays pending until Bitcoin confirms it, after which the agent can upgrade it and verify that the hash existed before a given Bitcoin block. Local hashing and proof inspection run without network calls, and a whitelisted local file can be checked against an external .ots proof without changing the local stamp store.
It suits workflows where timestamping, confirmation tracking and proof checking should happen inside a conversation with an agent. The CLI can also monitor pending stamps, run upgrade passes, schedule automatic upgrades at the OS level and back up the database.
Running it requires Node.js 20 or later. Setup writes the MCP entry into the agent's config file, keeping a backup if one exists, and the agent must be restarted afterwards. Stamp data is kept in a local SQLite database under ~/.ots-mcp/, and defaults can be overridden with a config.json file in that directory. The watch command defaults to 30 minutes with a 15-minute minimum.
Limitations and requirements
Requires Node.js 20 or later. Confirmations typically arrive within about 60 minutes but can take several hours during network congestion; a pending proof is not a failed proof. The watch command has a 15-minute minimum interval. The agent must be restarted after setup. verify_external_proof only works on whitelisted local files. This is an independent implementation, not affiliated with or maintained by the OpenTimestamps project.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.AlexAlves87/otskit-mcp
Stamp, upgrade, and verify Bitcoin timestamps via AI agents. No API keys required.
v0.2.1As shown on registry.modelcontextprotocol.io when we last read it