OpenTimeStamps MCP Server
Allows timestamping files and verifying cryptographic proofs on the Bitcoin blockchain via OpenTimeStamps calendars.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@OpenTimeStamps MCP Server timestamp the file 'notes.txt'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
π°οΈ OpenTimeStamps MCP Server
A Model Context Protocol (MCP) server that enables AI models to interact with OpenTimeStamps, allowing them to timestamp files and verify proofs on the Bitcoin blockchain.
Trustless timestamping for the AI age.
π Features
π’ Calculate hash values (SHA256, SHA1, RIPEMD160)
β° Submit hashes for timestamping via OpenTimeStamps calendars
π Load and parse OTS proof files
π Display detailed information about OTS proofs
β¬οΈ Upgrade incomplete OTS proofs
β Verify OTS proofs against original data or hashes
π Server-Sent Events (SSE) support for web integration
π MCP-compliant API for AI integration
Related MCP server: Nostr MCP Server
π Prerequisites
Node.js 18+
π οΈ Installation
Installing via Smithery (Coming Soon)
To install OpenTimeStamps MCP Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @fmar/opentimestamps-mcp --client claudeManual Installation
Clone the repository:
git clone https://github.com/fmargarita/opentimestamps-mcp
cd opentimestamps-mcpInstall dependencies:
npm installBuild the project:
npm run buildCreate a
.envfile (optional):
You can copy .env.example and modify as needed:
cp .env.example .envπ§ Setup with Claude Desktop
To use this MCP server with Claude Desktop, add the following to your Claude Desktop configuration file:
macOS
# Edit the configuration file
code ~/Library/Application\ Support/Claude/claude_desktop_config.jsonWindows
# Edit the configuration file
notepad %APPDATA%\Claude\claude_desktop_config.jsonConfiguration
Add this configuration to your claude_desktop_config.json:
{
"mcpServers": {
"opentimestamps": {
"command": "node",
"args": ["/absolute/path/to/opentimestamps-mcp/build/cli.js"],
"env": {
"LOG_LEVEL": "info"
}
}
}
}Important: Replace /absolute/path/to/opentimestamps-mcp/ with the actual path where you cloned this repository.
After updating the configuration:
Restart Claude Desktop
You should see the OpenTimeStamps tools available in your conversation
π§ Setup with Goose
For Goose AI assistant, add this to your config.yaml:
mcp:
servers:
opentimestamps:
command: node
args:
- /absolute/path/to/opentimestamps-mcp/build/cli.js
env:
LOG_LEVEL: infoπ¦ Usage
Starting the Server
# Development mode with hot reload
npm run dev
# Production mode
npm startAvailable Tools
calculate_hash
Calculate the hash of data using the specified algorithm.
Example input:
{
"data": "Hello, OpenTimeStamps!",
"algorithm": "sha256"
}stamp_hash
Submit a hash for timestamping using OpenTimeStamps calendar servers.
Example input:
{
"hash": "a665a45920422f9d417e4867efdc4fb8a04a1f3fff1fa07e998e86f7f7a27ae3",
"algorithm": "sha256"
}load_proof
Load an OTS proof from hex data or file path.
Example input:
{
"otsData": "004f70656e54696d657374616d7073000050726f6f66...",
"isFilePath": false
}get_proof_info
Display detailed information about an OTS proof.
Example input:
{
"otsData": "004f70656e54696d657374616d7073000050726f6f66..."
}upgrade_proof
Upgrade an incomplete OTS proof by fetching missing attestations.
Example input:
{
"otsData": "004f70656e54696d657374616d7073000050726f6f66..."
}verify_proof
Verify an OTS proof against original data or hash.
Example input:
{
"otsData": "004f70656e54696d657374616d7073000050726f6f66...",
"originalData": "Hello, OpenTimeStamps!",
"algorithm": "sha256"
}π§ Development
Project Structure
opentimestamps-mcp/
βββ src/
β βββ index.ts # Main server entry point
β βββ ots-client.ts # OpenTimeStamps client implementation
β βββ stdio_server.ts # STDIO transport server
β βββ sse_server.ts # SSE transport server
β βββ types.ts # TypeScript type definitions
β βββ types/ # Type declarations
β βββ utils/ # Utility functions
βββ .env.example # Environment configuration template
βββ claude_desktop_config.json # Claude Desktop config example
βββ tsconfig.json # TypeScript configurationRunning Tests
npm testπ Examples
Basic Workflow
Calculate a hash of your data:
Use the calculate_hash tool with your text or dataSubmit for timestamping:
Use the stamp_hash tool with the resulting hashCheck the proof:
Use get_proof_info to see the attestation detailsUpgrade proof (after ~10 minutes):
Use upgrade_proof to get Bitcoin confirmationsVerify the proof:
Use verify_proof with your original data and the proof
Sample Conversation with Claude
User: "Please calculate the SHA256 hash of 'Hello World'"
Claude will use: calculate_hash
Input: {"data": "Hello World", "algorithm": "sha256"}
User: "Now timestamp that hash"
Claude will use: stamp_hash
Input: {"hash": "a591a6d40bf420404a011733cfb7b190d62c65bf0bcda32b57b277d9ad9f146e", "algorithm": "sha256"}
User: "Show me the proof information"
Claude will use: get_proof_info
Input: {"otsData": "004f70656e54696d657..."}π Privacy & Security
OpenTimeStamps provides cryptographic proof of existence without revealing file contents:
Privacy: Only file hashes are submitted to calendar servers, never the actual data
Trustless: Verification is done against the Bitcoin blockchain, not trusted third parties
Immutable: Once timestamped on Bitcoin, proofs cannot be altered or removed
Verifiable: Anyone can independently verify timestamps using the Bitcoin blockchain
βοΈ Configuration
All configuration is optional and handled through environment variables:
OTS_CALENDAR_SERVERS: Custom calendar servers (defaults to standard OTS servers)BITCOIN_RPC_*: Bitcoin node connection for local verification (optional)SERVER_MODE: Choose betweenstdio(default) orssetransportPORT: HTTP port for SSE mode (default: 3000)
π€ Contributing
Fork the repository
Create your feature branch (
git checkout -b feature/amazing-feature)Commit your changes (
git commit -m 'Add some amazing feature')Push to the branch (
git push origin feature/amazing-feature)Open a Pull Request
π License
This project is licensed under the MIT License - see the LICENSE file for details.
π Resources
π Getting Started
The fastest way to test the server:
Calculate a hash:
"Calculate the SHA256 hash of 'Hello World'"Timestamp the hash:
"Timestamp that hash using OpenTimeStamps"Verify later:
"Verify the proof against the original text 'Hello World'"
Available Tools
7 toolscalculate_hashC
Calculate the hash of data using the specified algorithm (sha256, sha1, or ripemd160)
Inputs: data (required), algorithm.
get_full_proofC
Get the full OTS proof from a given hash
Inputs: hash (required), algorithm.
get_proof_infoC
Display information about an OTS proof
Inputs: otsData (required).
load_proofB
Load an OTS proof from hex data or file path
Inputs: otsData (required), isFilePath.
stamp_hashC
Submit a hash for timestamping using OpenTimeStamps calendar servers
Inputs: hash (required), algorithm.
upgrade_proofA
Upgrade an incomplete OTS proof by fetching missing attestations
Inputs: otsData (required).
verify_proofC
Verify an OTS proof against original data or hash
Inputs: otsData (required), algorithm, originalData, originalHash.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 7 tools
Each tool maps to a distinct step in the OpenTimestamps workflow (hash, stamp, load, info, upgrade, verify, retrieve). The only potential overlap is load_proof vs get_full_proof, but their descriptions distinguish inputs (hex/file vs hash), so confusion is limited.
All tool names use snake_case with a verb-first pattern (calculate_hash, stamp_hash, load_proof, upgrade_proof, verify_proof, etc.). The naming is predictable and consistent across the set.
Seven tools is well-scoped for the OpenTimestamps lifecycle; each operation serves a distinct purpose without redundancy. The count fits comfortably within the recommended 3β15 range.
Core lifecycle operationsβhashing, stamping, loading/retrieving proofs, inspecting, upgrading, and verifyingβare all covered. A minor gap is the lack of an explicit save/export proof tool, though load_proof and get_full_proof may cover retrieval needs.
Maintenance
Related MCP Connectors
Tamper-evident proof creation and verification for AI agents via MCP, A2A, and REST.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yoβ¦
Signed, Merkle-proofed, on-chain-anchored trust records for MCP servers. Verify, do not trust.
Signed, Bitcoin-anchored observations of AI training-data disclosure; verifies silence proofs, seals
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server enabling AI models to interact with the Nostr network, facilitating note posting and interaction with the freedom of speech protocol.39MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI models to interact with the Nostr network, allowing them to post notes and eventually send Lightning zaps to users.1MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that provides real-time Bitcoin blockchain and mempool data to AI clients, allowing access to comprehensive Bitcoin network information through various data tools.3115 npm5MIT
- AlicenseAqualityDmaintenanceDocument verification MCP server enabling AI agents to verify file authenticity by computing SHA-256 fingerprints locally and checking Bitcoin-anchored proofs via OpenTimestamps.55 npmMIT