Témoin public
REMOTE · TEMOINPUBLIC.FR
Prove a web page or document existed on a date: public SHA-256 registry anchored in Bitcoin. Free.
Available components
Last scanned (2 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Documents and Files
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 426 tokens (~106/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 16 Oct 26 +1
- Tool “lire_recu” rewrote its description, which is the text the model reads security
- 14 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 13 Oct 26 62
First indexed and scored.
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 17 Oct 2026 · Probed https://temoinpublic.fr/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=temoinpublic.fr | CN=WE1,O=Google Trust Services,C=US | 12 Oct 2026 | 10 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 99e12b63d5130dfa13bf1359e5d814bc |
| SANs: temoinpublic.fr | ||||||
| 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 temoinpublic.fr. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| fr. | present | 65381 | 13 | Verified |
| temoinpublic.fr. | 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://temoinpublic.fr/mcp | Verified | 200 | |
| http (plaintext) | http://temoinpublic.fr/mcp | HTTPS enforced | 301 | https://temoinpublic.fr/mcp |
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 →
chercher_empreinte Trouver les dates d’un document ~69
Rend chaque dépôt de cette empreinte SHA-256 : jour, ligne du registre, adresse du reçu. Aucun dépôt : le document n’a pas été daté par ce service.
| Name | Type | Req | Description |
|---|---|---|---|
| sha256 | string | yes | Empreinte SHA-256, 64 caractères hexadécimaux. |
No output schema declared.
No examples provided.
dater_empreinte Dater un document par son empreinte ~103
Inscrit dans le registre public l’empreinte SHA-256 d’un document que l’utilisateur garde ; le document n’est jamais envoyé. Rend le reçu, qui prouve que ce document existait à cette date, sans modification.
| Name | Type | Req | Description |
|---|---|---|---|
| libelle | string | – | Un nom pour s’y retrouver ; il reste dans le reçu, jamais publié. |
| sha256 | string | yes | Empreinte SHA-256, 64 caractères hexadécimaux. |
No output schema declared.
No examples provided.
dater_url Dater une page ou un document en ligne ~123
Le service lit lui-même l’adresse publique (http ou https, 20 Mo et 30 s au plus) et inscrit l’empreinte SHA-256 des octets lus dans le registre public, ancré dans Bitcoin. Rend le reçu : à remettre à l’utilisateur, il prouve que ce contenu était servi à cette adresse à cet instant. Une même adresse se lit une fois par jour.
| Name | Type | Req | Description |
|---|---|---|---|
| libelle | string | – | Un nom pour s’y retrouver ; il reste dans le reçu, jamais publié. |
| url | string | yes | Adresse publique à lire. |
No output schema declared.
No examples provided.
lire_recu Lire un reçu ~62
Rend la ligne publique d’un reçu par son identifiant (64 caractères hexadécimaux) : empreinte, jour, ligne du registre, et pour un acte de collectivité son adresse pérenne, à citer.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Témoin public MCP server?
Témoin public is a hosted endpoint at https://temoinpublic.fr/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 · temoinpublic.fr
claude mcp add --transport http fr-temoinpublic-temoinpublic 'https://temoinpublic.fr/mcp'
What is the Témoin public MCP server?
Témoin public is an MCP server listed in the public MCP registry as fr.temoinpublic/temoinpublic. Prove a web page or document existed on a date: public SHA-256 registry anchored in Bitcoin. Free. This page covers its hosted endpoint (https://temoinpublic.fr/mcp).
Is the Témoin public MCP server safe to use?
Témoin public scores 64 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 Témoin public MCP server expose?
Témoin public exposes 4 tools: dater_url, dater_empreinte, chercher_empreinte, lire_recu. Their descriptions and schemas cost roughly 357 tokens of context every time the server is loaded.
Does the Témoin public MCP server require authentication?
No. We connected to Témoin public without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Témoin public MCP server still maintained?
Témoin public is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.