Back to Browse

Tithonus MCP Server

by Llamr
Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

Signed time, Bitcoin-anchored notarisation and drand randomness for agents. No account.

About

Signed time, Bitcoin-anchored notarisation and drand randomness for agents. No account.

Remote endpoints: streamable-http: https://tithonus.org/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 0 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

5 tools verified · Open access · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

file_system

Applies to the server that hosts this plugin, not to your machine.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "org-tithonus-mcp": {
      "url": "https://tithonus.org/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

README.md

tithonus.org

Time and proof for agents. The source of tithonus.org.

Signed time, notarisation and public randomness, with every stamp anchored in Bitcoin through OpenTimestamps. One Cloudflare Worker, no dependencies, no build step. Every feature is one plain GET; the same tools are also served over MCP at /mcp.

The live manual is the homepage: curl https://tithonus.org/

Trust model

  • Until a stamp is anchored, it rests on the operator's Ed25519 key (/keys).
  • Once anchored (hourly batches, then usually within hours), its .ots proof verifies against Bitcoin alone, with no tithonus involved.
  • Service health is published, signed, at /stats. Every batch is published, signed, at /batches, and copied hourly by an outside witness: llamr/tithonus.org-witness.
  • tithonus proves when something existed and that it is unaltered. It never proves that a claim is true.

Run your own copy

Anyone may run a mirror. Proofs from any copy verify the same way.

npx wrangler d1 create tithonus          # put the database_id it prints into wrangler.toml
npx wrangler d1 execute tithonus --remote --file=schema.sql
node -e "crypto.subtle.generateKey({name:'Ed25519'},true,['sign']).then(k=>crypto.subtle.exportKey('jwk',k.privateKey)).then(j=>console.log(JSON.stringify(j)))" | npx wrangler secret put SIGNING_KEY
npx wrangler deploy

Change routes in wrangler.toml to your own domain first.

Privacy

Logs keep only the day, the service used and a coarse vendor label from the user agent. No IP addresses, no hashes, no content. Text sent to /stamp is salted and hashed in memory and never stored.

Reviews

No reviews yet

Be the first to review this server!