Remote MCP · Endpoint

Témoin public MCP server

No. Témoin public answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://temoinpublic.fr/mcp

The last check completed an MCP handshake.

Registry name
fr.temoinpublic/temoinpublic
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
856 ms
Tools exposed
4 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Prove a web page or document existed on a date: public SHA-256 registry anchored in Bitcoin. Free.
Listing
From the official MCP registry (active).
Recent checks of Témoin public
CheckedResultHandshake
20 minutes agoHandshake completed856 ms
9 days agoHandshake completed412 ms
9 days agoHandshake completed421 ms
11 days agoHandshake completed398 ms
12 days agoHandshake completed655 ms
13 days agoHandshake completed428 ms
14 days agoHandshake completed427 ms
14 days agoHandshake completed415 ms
16 days agoHandshake completed371 ms
19 days agoHandshake completed543 ms
21 days agoFailed - the server returned an HTTP error—
24 days agoHandshake completed731 ms
26 days agoHandshake completed102 ms
28 days agoHandshake completed102 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 16.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Témoin public and makes no claim about it beyond what these checks measured.