Otskit Mcp

io.github.AlexAlves87Published by GitHub account AlexAlves87v0.2.1Updated Oct 24, 2026

Stamp, upgrade, and verify Bitcoin timestamps via AI agents. No API keys required.

VerifiedSTDIODesktop onlyFinance Developer Tools

Server details

Identifier: io.github.AlexAlves87/otskit-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account AlexAlves87 for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.AlexAlves87%2Fotskit-mcp.svg)](https://sourceweft.com/mcp/io.github.AlexAlves87%2Fotskit-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server that lets an AI assistant stamp files or SHA-256 hashes with OpenTimestamps, check Bitcoin confirmation, and verify proofs.

What you can do: Stamp a SHA-256 hash or a local file against public OpenTimestamps calendars and store the proof locally. Check pending stamps for Bitcoin confirmation and upgrade them. Verify stored stamps or an external .ots proof file against the Bitcoin blockchain. Inspect stored proofs offline, list stamps by status, and compute a file's SHA-256 hash.
When to use it: Useful when you want an assistant to prove that a document or hash existed before a certain Bitcoin block, or to track and verify OpenTimestamps proofs from a conversation instead of the command line.
Requirements: Runs as a local process via npm package @otskit/mcp with Node.js 20 or later. No API keys are needed. It needs network access to public OpenTimestamps calendars and writes data to a local directory under the user's home folder.

Before you install

Stamping sends the SHA-256 hash of your file to public OpenTimestamps calendars, so the hash becomes visible to third parties. Proofs stay pending until Bitcoin confirms them, which can take hours. The server writes a local SQLite database and can modify agent config files during setup, keeping a backup.

Installation

In SourceWeft

Open Otskit Mcp in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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

Agent setup

bash

ots-mcp setup claude        # Claude Desktopots-mcp setup claude-code   # Claude Code CLIots-mcp setup codex         # Codex CLI

ots-mcp setup claude        # Claude Desktopots-mcp setup claude-code   # Claude Code CLIots-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/:

text

~/.ots-mcp/  ots-mcp.db       # SQLite database (stamps, proof files)  config.json      # Optional config overrides  ots-mcp.log      # Log file

~/.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:

json

{  "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"  ]}

{  "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

Dependencies

@otskit/client - OTS calendar client (brings in @otskit/core, the protocol engine)
@modelcontextprotocol/sdk - MCP SDK
node-sqlite3-wasm - local database (pure WASM, no native compilation)

Requires Node.js >= 20.

Source: README.md at commit 39799bd

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.2.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts