Otskit Mcp
Anchor release artifacts, contracts, or config hashes to Bitcoin via OpenTimestamps from your coding agent without managing keys or a paid API.
Overview
OTSkit MCP is a MCP server for the Ship phase that stamps, upgrades, and verifies Bitcoin OpenTimestamps proofs for files and hashes through your agent.
What is this MCP server?
- Stamp files or hashes with OpenTimestamps directly from MCP tools
- Upgrade pending timestamps as Bitcoin confirmations mature
- Verify existing .ots proofs against originals
- Stdio npm package @otskit/mcp v0.2.1—no API keys required
- GitHub source at OTSkit/OTSkit-MCP for self-hosted stdio wiring
- Server version 0.2.1 on npm package @otskit/mcp
- Transport: stdio only in published registry metadata
- No API keys required per server description
What problem does it solve?
You need cryptographic proof that a document or build artifact existed at a specific time, but notary services and custom Bitcoin tooling are too heavy for a one-person workflow.
Who is it for?
Indie builders who want OpenTimestamps from the agent that already handles releases, backups, or legal snapshots.
Skip if: Teams that need enterprise PKI, GDPR-focused EU-only retention, or timestamping without any Bitcoin exposure.
What do I get? / Deliverables
Your agent can create and verify .ots-backed timestamps locally so shipped artifacts carry auditable, Bitcoin-anchored existence proofs.
- New or upgraded OpenTimestamps proofs tied to your artifacts
- Verification results comparing originals to .ots attestations
Recommended MCP Servers
Journey fit
Timestamp proofs matter most when you are shipping something you may need to defend later—releases, legal docs, or integrity checks before and after launch. Security subphase covers tamper-evident evidence and verification workflows that complement signing and audit trails, not general backend coding.
How it compares
MCP integration for OpenTimestamps, not a general secrets scanner or CI signing plugin.
Common Questions / FAQ
Who is OTSkit MCP for?
Solo and indie developers using MCP agents who want Bitcoin-backed timestamp stamp, upgrade, and verify flows without API keys.
When should I use OTSkit MCP?
Use it during ship and security review when you need to prove when a file, hash, or release bundle existed before sharing or disputing changes.
How do I add OTSkit MCP to my agent?
Install @otskit/mcp from npm, add the stdio MCP server entry pointing at that package in Claude Code or Cursor, and invoke the stamp, upgrade, and verify tools from the agent.