Allows AI agents to stamp, upgrade, and verify document proofs against the Bitcoin blockchain using the OpenTimestamps protocol.
Also known as OTSkit/OTSkit-MCP, @otskit/mcp
- Stars
- 3
- Tools
- 9
- Downloads, 30 days
- —
- Latest version
- 0.2.1
- Last commit
- Nov 12, 2026
- License
- MIT
What is OTSkit MCP?
OTSkit allows AI agents to stamp, upgrade, and verify document proofs against the Bitcoin blockchain using the OpenTimestamps protocol. It exposes 9 tools, such as create_timestamp, upgrade_timestamp, verify_timestamp.
Summary generated from the project's README
About OTSkit MCP server
Timestamping documents against the Bitcoin blockchain is what developers achieve using this MCP server. It provides AI agents with the ability to create, monitor, and validate proofs using the OpenTimestamps protocol. By connecting to agents like Claude Desktop, Claude Code, or Codex, the server allows for the creation of immutable records through SHA-256 hashing and Bitcoin calendar integration.
Users interact with the server via tools such as stamp_file to hash and timestamp local files in a single step, or verify_timestamp to prove a hash existed before a specific Bitcoin block. The system manages data locally using a SQLite database in the user directory and handles the transition of proofs from a pending state to confirmed status. It includes specialized functions like watch to monitor network confirmations and upgrade_timestamp to check for Bitcoin block inclusion, ensuring that agents can manage the lifecycle of a proof without manual intervention.
Written from the project's README. Every use case is checked against a quote from it.
How to install OTSkit MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall OTSkit MCP in Claude Code
$ claude mcp add otskit-mcp -- npx -y @otskit/mcpInstall OTSkit MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"otskit-mcp": {
"command": "npx",
"args": [
"-y",
"@otskit/mcp"
]
}
}
}Install OTSkit MCP in VS Code
.vscode/mcp.json
{
"servers": {
"otskit-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@otskit/mcp"
]
}
}
}Install OTSkit MCP in VS Code CLI
$ code --add-mcp '{"name":"otskit-mcp","type":"stdio","command":"npx","args":["-y","@otskit/mcp"]}'Install OTSkit MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"otskit-mcp": {
"command": "npx",
"args": [
"-y",
"@otskit/mcp"
]
}
}
}Install OTSkit MCP in Codex
$ codex mcp add otskit-mcp -- npx -y @otskit/mcpInstall OTSkit MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.otskit-mcp] command = "npx" args = ["-y", "@otskit/mcp"]
Install OTSkit MCP in Gemini CLI
$ gemini mcp add -s user otskit-mcp npx -- -y @otskit/mcpInstall OTSkit MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"otskit-mcp": {
"command": "npx",
"args": [
"-y",
"@otskit/mcp"
]
}
}
}OTSkit MCP tools 9
Detected from the READMEcreate_timestampupgrade_timestampverify_timestampverify_external_proofinspect_timestamplist_pendingwatchhash_filestamp_file
| create_timestamp | — | |
| upgrade_timestamp | — | |
| verify_timestamp | — | |
| verify_external_proof | — | |
| inspect_timestamp | — | |
| list_pending | — | |
| watch | — | |
| hash_file | — | |
| stamp_file | — |
Automated checks
Ran Nov 13, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledPass
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHub@otskit/mcp
OpenTimestamps MCP server - stamp, upgrade, and verify Bitcoin timestamps via AI agents.
Exposes a set of tools to any MCP-compatible agent so it can timestamp documents, monitor confirmation status, and verify proofs against the Bitcoin blockchain - all from a conversation.
This is an independent implementation of the OpenTimestamps protocol. It is not affiliated with, endorsed by, or maintained by the OpenTimestamps project.
Note on confirmation times: After stamping, a proof is
pendinguntil Bitcoin confirms it. Confirmations typically arrive within ~60 minutes, but can take several hours during network congestion. Useots-mcp watchorupgrade_timestampto monitor. A pending proof is not a failed proof.
Install
npm install -g @otskit/mcp
Agent setup
ots-mcp setup claude # Claude Desktop
ots-mcp setup claude-code # Claude Code CLI
ots-mcp setup codex # Codex CLI
Each command writes the MCP entry into the agent's config file, makes a .bak backup if the file already exists, and skips if ots-mcp is already configured. Restart the agent afterwards to apply the changes.
CLI commands
| Command | Description |
|---|---|
ots-mcp serve |
Start the MCP server (stdio transport) |
ots-mcp stamp <sha256> |
Stamp a SHA-256 hash against Bitcoin calendars |
ots-mcp upgrade <id> |
Check if a pending stamp has been confirmed |
ots-mcp verify <id> |
Verify a stamp against Bitcoin |
ots-mcp list [status] |
List stamps (pending / confirmed / failed) |
ots-mcp watch [minutes] |
Monitor pending stamps and attempt due upgrades (default: 30 min, minimum: 15 min) |
ots-mcp check-pending |
Run one upgrade pass over all pending stamps |
ots-mcp scheduler install|remove|status |
Manage OS-level scheduler for auto-upgrades |
ots-mcp backup [dest] |
Backup the SQLite database |
ots-mcp setup <claude|claude-code|codex> |
Configure MCP for an agent |
MCP tools exposed to agents
| Tool | Description |
|---|---|
create_timestamp |
Stamp a SHA-256 hash against 4 public OTS calendars |
upgrade_timestamp |
Check if a pending stamp has been confirmed in Bitcoin |
verify_timestamp |
Verify a stamp - proves hash existed before a given Bitcoin block |
verify_external_proof |
Verify a whitelisted local file against its external .ots proof, without changing the local stamp store |
inspect_timestamp |
Inspect a stored proof file without network calls |
list_pending |
List stamps with status, retry count, and filters |
watch |
Open a terminal window monitoring pending stamps and attempting due upgrades |
hash_file |
Compute the SHA-256 of a local file and return it as a 64-char hex string (no network calls) |
stamp_file |
Compute SHA-256 of a local file and stamp it on Bitcoin in one step |
Data directory
All data is stored in ~/.ots-mcp/:
~/.ots-mcp/
ots-mcp.db # SQLite database (stamps, proof files)
config.json # Optional config overrides
ots-mcp.log # Log file
Configuration
Create ~/.ots-mcp/config.json to override defaults:
{
"stamp_enabled": true,
"scheduler_interval_minutes": 30,
"retry_max_attempts": 20,
"calendar_timeout_ms": 10000,
"calendars": [
"https://alice.btc.calendar.opentimestamps.org",
"https://bob.btc.calendar.opentimestamps.org",
"https://finney.calendar.eternitywall.com",
"https://btc.calendar.catallaxy.com"
]
}
Development
npm run build # production build
npm run dev # watch mode
npm test # run tests
Dependencies
@otskit/client- OTS calendar client (brings in@otskit/core, the protocol engine)@modelcontextprotocol/sdk- MCP SDKnode-sqlite3-wasm- local database (pure WASM, no native compilation)
Requires Node.js >= 20.
OTSkit MCP questions
How do I add OTSkit MCP to Claude Code?
Run claude mcp add otskit-mcp -- npx -y @otskit/mcp in your terminal. Add --scope user to make it available in every project.
How do I add OTSkit MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does OTSkit MCP provide?
It exposes 9 tools, including create_timestamp, upgrade_timestamp, verify_timestamp, verify_external_proof, inspect_timestamp.
Where is the data stored?
All data, including the SQLite database and log files, is stored in the ~/.ots-mcp/ directory.