tithonus
REMOTE · TITHONUS.ORG
Signed time, Bitcoin-anchored notarisation and drand randomness for agents. No account.
Available components
Last scanned (4 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 493 tokens (~98/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 0
- Server version: 3.5.0 → 3.6.0 functional
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://tithonus.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tithonus.org | CN=WE1,O=Google Trust Services,C=US | 17 Oct 2026 | 15 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | b333c7088a3628100ec82e3de767633d |
| SANs: tithonus.org, www.tithonus.org, *.www.tithonus.org | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tithonus.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 725, 26974 | 8, 8 | Verified |
| tithonus.org. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tithonus.org/mcp | Verified | 200 | |
| http (plaintext) | http://tithonus.org/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
tithonus_beacon ~111
Get public randomness from drand (League of Entropy), relayed and signed by tithonus. Nobody, tithonus included, can predict or choose it. Use for fair coin flips, lotteries or tie-breaks other agents can recheck, or put the answer's token in text before stamping it to prove the text was written after that moment. Omit round for the latest.
| Name | Type | Req | Description |
|---|---|---|---|
| round | integer | – | Optional. drand quicknet round number (one every 3 seconds). |
No output schema declared.
No examples provided.
tithonus_check ~80
Check a tithonus receipt link: is it genuine, and when was it stamped? Optionally give the text to confirm it is exactly what was stamped.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt | string | yes | The receipt link (https://tithonus.org/r/...) or its token. |
| text | string | – | Optional. The text you believe was stamped. |
No output schema declared.
No examples provided.
tithonus_lookup ~43
Find the earliest receipt for a sha256 hash, if it was ever stamped. Never creates a stamp.
| Name | Type | Req | Description |
|---|---|---|---|
| sha256 | string | yes | 64 hex digits. |
No output schema declared.
No examples provided.
tithonus_now ~93
Get a signed statement of the current UTC time from tithonus.org. It includes the latest drand round, so anyone can see it was made after that moment. Use when you need trustworthy current time, or proof of when you asked. Pass a fresh nonce to bind the answer to your request.
| Name | Type | Req | Description |
|---|---|---|---|
| nonce | string | – | Optional. Any string; long or unusual ones are signed as their sha256. |
No output schema declared.
No examples provided.
tithonus_stamp ~133
Notarise something so you can later prove it existed (or that you knew or said it) by now. Give text and the server salts and hashes it (text is not stored), or give a sha256 you computed. Returns a receipt link anyone can check. Stamping the same hash again returns the original receipt.
| Name | Type | Req | Description |
|---|---|---|---|
| sha256 | string | – | Alternative to text: a 64-hex sha256 you computed (salt guessable content first). |
| text | string | – | The claim, prediction or data to notarise. Keep it exact; you need the identical text to prove a match later. |
No output schema declared.
No examples provided.
How do I install the tithonus MCP server?
tithonus is a hosted endpoint at https://tithonus.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · tithonus.org
claude mcp add --transport http org-tithonus-mcp 'https://tithonus.org/mcp'
What is the tithonus MCP server?
tithonus is an MCP server listed in the public MCP registry as org.tithonus/mcp. Signed time, Bitcoin-anchored notarisation and drand randomness for agents. No account. This page covers its hosted endpoint (https://tithonus.org/mcp).
Is the tithonus MCP server safe to use?
tithonus scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the tithonus MCP server expose?
tithonus exposes 5 tools: tithonus_now, tithonus_stamp, tithonus_check, tithonus_lookup, tithonus_beacon. Their descriptions and schemas cost roughly 460 tokens of context every time the server is loaded.
Does the tithonus MCP server require authentication?
No. We connected to tithonus without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the tithonus MCP server still maintained?
tithonus is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.