VOOZH about

URL: https://glama.ai/mcp/servers/search/open-timestamps-bitcoin-based-timestamping-protocol

⇱ OpenTimestamps - Bitcoin-based timestamping protocol | Glama

Search for:

OpenTimestamps - Bitcoin-based timestamping protocol

View all MCP Servers

  • Why this server?

    Directly uses OpenTimestamps to anchor SHA-256 fingerprints on Bitcoin, enabling file authenticity verification.

    A
    license
    A
    quality
    C
    maintenance
    Document verification MCP server enabling AI agents to verify file authenticity by computing SHA-256 fingerprints locally and checking Bitcoin-anchored proofs via OpenTimestamps.
    Last updated
    5
    1
    MIT

  • Why this server?

    Provides cryptographic Proof of Time using multiple independent time sources, similar in concept to OpenTimestamps.

    A
    license
    A
    quality
    B
    maintenance
    MCP Server for OpenTTT — Proof of Time tools for AI agents AI Agent A and Agent B both trigger a payment at the same time. Who was first? OpenTTT answers this with cryptographic Proof of Time — synthesized from multiple independent time sources, verified through GRG integrity shards, and signed with Ed25519 for non-repudiation.
    Last updated
    5
    54
    Business Source 1.1

  • Why this server?

    Enables Bitcoin timestamps via OP_RETURN, allowing embedding and reading data on-chain for timestamping purposes.

    F
    license
    B
    quality
    F
    maintenance
    Enables interaction with Bitcoin's blockchain through Claude to embed and read data using OP_RETURN, create timestamps, deploy BRC-20 tokens, and store documents up to 100KB on-chain.
    Last updated
    16
    2

  • Why this server?

    Creates tamper-evident receipts for AI agent actions, leveraging cryptographic proofs for verifiable timestamping.

  • Why this server?

    Captures web pages with RFC 3161 timestamps and Ed25519 signatures, providing verifiable evidence.

    A
    license
    -
    quality
    F
    maintenance
    📇 ☁️ - Capture web pages as cryptographically signed, tamper-evident evidence. Ed25519 signatures, RFC 3161 timestamps, and WACZ archives. Four tools: capture_url, get_capture, list_captures, verify_capture.
    Last updated
    3
    1
    MIT

  • Why this server?

    Records agent actions in a SHA-256 hash chain, enabling provenance and timestamp verification.

    A
    license
    A
    quality
    A
    maintenance
    Every agent action is recorded in a SHA-256 hash chain. Prove to clients that your agent did what it said it did. Record, query, verify, and export agent activity.
    Last updated
    3
    36
    1
    MIT

  • Why this server?

    Offers tamper-proof audit trails with cryptographic proof chains, useful for timestamping AI decisions.

    A
    license
    -
    quality
    C
    maintenance
    Tamper-proof audit trail for AI decisions. 6 tools to record, verify, and export cryptographic proof chains via MCP.
    Last updated
    1
    Apache 2.0

  • Why this server?

    Signs HTTP calls with Ed25519 and RFC 3161 timestamps, plus Sigstore Rekor anchoring for verifiable timestamps.

    A
    license
    A
    quality
    B
    maintenance
    Third-party certifying proxy — sign any HTTP call (AI agents, webhooks, microservices) with an independent Ed25519 signature, RFC 3161 timestamp, and Sigstore Rekor anchor.
    Last updated
    4
    1
    MIT

  • Why this server?

    Stores a timestamped audit trail for AI conversations, providing local, owned timestamp records.

    F
    license
    A
    quality
    B
    maintenance
    A timestamped audit trail for every AI conversation — stored locally, owned by you.
    Last updated
    6
    268
    1