Skip to main content
Glama
getAlby

OpenTimeStamps MCP Server

by getAlby

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PORTNoHTTP port for SSE mode (default: 3000)3000
LOG_LEVELNoLogging level (e.g., info, debug)info
SERVER_MODENoTransport mode: stdio or sse (default: stdio)stdio
BITCOIN_RPC_URLNoBitcoin node RPC URL for local verification (optional)
BITCOIN_RPC_USERNoBitcoin node RPC username (optional)
BITCOIN_RPC_PASSWORDNoBitcoin node RPC password (optional)
OTS_CALENDAR_SERVERSNoCustom 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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 7 tools

Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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

ActivityInactive
ResponsivenessNo issues