Remote MCP · Endpoint

MachineWitness MCP server

No. MachineWitness answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://machinewitness.eu/mcp

The last check completed an MCP handshake.

Registry name
eu.machinewitness/archive
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
508 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
EU archive of the machine-readable web: check a domain, order a time-stamped record or extract.
Listing
From the official MCP registry (active).
Recent checks of MachineWitness
CheckedResultHandshake
1 hour agoHandshake completed508 ms
2 days agoHandshake completed168 ms
5 days agoHandshake completed77 ms
7 days agoHandshake completed153 ms
9 days agoHandshake completed131 ms
11 days agoHandshake completed126 ms
13 days agoHandshake completed82 ms
15 days agoHandshake completed380 ms
17 days agoHandshake completed122 ms
19 days agoHandshake completed77 ms
20 days agoHandshake completed175 ms
21 days agoHandshake completed124 ms
22 days agoHandshake completed205 ms

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

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 MachineWitness and makes no claim about it beyond what these checks measured.