OpenTimeStamps MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP port for SSE mode (default: 3000) | 3000 |
| LOG_LEVEL | No | Logging level (e.g., info, debug) | info |
| SERVER_MODE | No | Transport mode: stdio or sse (default: stdio) | stdio |
| BITCOIN_RPC_URL | No | Bitcoin node RPC URL for local verification (optional) | |
| BITCOIN_RPC_USER | No | Bitcoin node RPC username (optional) | |
| BITCOIN_RPC_PASSWORD | No | Bitcoin node RPC password (optional) | |
| OTS_CALENDAR_SERVERS | No | Custom calendar servers (defaults to standard OTS servers) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| calculate_hashC | Calculate the hash of data using the specified algorithm (sha256, sha1, or ripemd160) |
| stamp_hashC | Submit a hash for timestamping using OpenTimeStamps calendar servers |
| load_proofB | Load an OTS proof from hex data or file path |
| get_proof_infoC | Display information about an OTS proof |
| upgrade_proofA | Upgrade an incomplete OTS proof by fetching missing attestations |
| verify_proofC | Verify an OTS proof against original data or hash |
| get_full_proofC | Get the full OTS proof from a given hash |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.