mcpField
O
otskit-mcp

otskit-mcp

Local
github.com/OTSkitSecurity3Updated 2d ago
Repository

About otskit-mcp

otskit-mcp is an OpenTimestamps server for agents that stamp document hashes on Bitcoin and manage timestamp proofs. Its tools cover creation, confirmation monitoring, and verification, including local files and external proofs.

Key features

  1. 01Create Bitcoin timestamps
  2. 02Upgrade pending proofs
  3. 03Verify timestamp proofs
  4. 04Inspect and list stored stamps
  5. 05Hash and stamp local files
  6. 06Monitor pending upgrades

Use cases

  1. 01Timestamp a document hash
  2. 02Check whether a proof is confirmed
  3. 03Verify a file against an external proof
  4. 04Track pending stamps and retries

MCP support

The server exposes timestamp creation, upgrades, verification, inspection, listing, watching, and file hashing tools to MCP-compatible agents.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "alexalves87-otskit": {
      "command": "npx",
      "args": [
        "-y",
        "@otskit/mcp"
      ]
    }
  }
}
Run commandnpx -y @otskit/mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@otskit/mcp0.2.1

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

OTSkit MCP

@otskit/mcp

CI npm version npm downloads TypeScript Node Coverage Quality Gate License smithery badge

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.

OTSkit MCP server on Glama — security, license and quality rating plus download count

Note on confirmation times: After stamping, a proof is pending until Bitcoin confirms it. Confirmations typically arrive within ~60 minutes, but can take several hours during network congestion. Use ots-mcp watch or upgrade_timestamp to 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

CommandDescription
ots-mcp serveStart 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-pendingRun one upgrade pass over all pending stamps
ots-mcp scheduler install|remove|statusManage 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

ToolDescription
create_timestampStamp a SHA-256 hash against 4 public OTS calendars
upgrade_timestampCheck if a pending stamp has been confirmed in Bitcoin
verify_timestampVerify a stamp - proves hash existed before a given Bitcoin block
verify_external_proofVerify a whitelisted local file against its external .ots proof, without changing the local stamp store
inspect_timestampInspect a stored proof file without network calls
list_pendingList stamps with status, retry count, and filters
watchOpen a terminal window monitoring pending stamps and attempting due upgrades
hash_fileCompute the SHA-256 of a local file and return it as a 64-char hex string (no network calls)
stamp_fileCompute 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

Requires Node.js >= 20.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.