otskit-mcp
Related Servers
Alternatives to otskit-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to timestamp files in Bitcoin by submitting only their SHA-256 hashes, paying per hash in USDC via x402, and retrieving or verifying OpenTimestamps .ots proofs without an account or API key.MIT
- AlicenseAqualityBmaintenanceStamp and verify Bitcoin-anchored OpenTimestamps memory receipts for AI agents (stamp_memory / verify_receipt).2MIT
- AlicenseAqualityCmaintenanceThe open registry of AI agents. Every agent gets a free birth certificate (a number and a date) and can timestamp what it creates, or only its SHA-256, with an RFC 3161 timestamp and a Bitcoin anchor that anyone can verify without us. Free, no account.11MIT
- AlicenseAqualityBmaintenanceAppend-only evidence receipts for AI records: seal, verify, cite, chain-check, anchor status. A seal proves a record existed at a time, not that its contents are true. Five tools over stdio with npx -y apex-psi-mcp — no account, no key, verification free forever.569 npm1MIT

Proof-100 MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to timestamp SHA-256 fingerprints or short text on the BitcoinZ blockchain via shielded transactions, returning transaction IDs and viewing keys, and to check proof balance and deposit address.MIT- AlicenseNot gradedqualityDmaintenanceEnables AI agents to create document timestamps on a VerusID, writing directly to the Verus blockchain via a local or remote daemon.54 npmMIT
TDQS
Scored across 9 tools
Each tool maps to a distinct stage of the timestamping workflow: hashing, stamping, monitoring, upgrading, and verifying. Even the overlapping create_timestamp and stamp_file are clearly differentiated as hash-based vs. file convenience operations.
Most tools follow a clear verb_noun snake_case pattern such as hash_file, create_timestamp, and verify_external_proof. The single-verb watch and adjective-based list_pending are minor deviations from an otherwise predictable scheme.
Nine tools is a well-scoped count for an OpenTimestamps-based server. Each tool serves a meaningful step in the lifecycle without unnecessary redundancy, and the convenience tools are justified by common workflows.
The tool set covers the full OpenTimestamps lifecycle: hashing, creating timestamps, stamping files, listing pending proofs, upgrading, and verifying both internal and external proofs. No critical missing operation is apparent for the domain.