Remote MCP · Endpoint

Mark MCP server

No. Mark answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://makemark.io/mcp

The last check completed an MCP handshake.

Registry name
dev.tatastu/proof
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
423 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Mark: stamp files with a signed, timestamped provenance record. Hash locally; verify free.
Listing
From the official MCP registry (active).
Recent checks of Mark
CheckedResultHandshake
42 minutes agoHandshake completed423 ms
3 days agoHandshake completed745 ms
12 days agoHandshake completed510 ms
12 days agoHandshake completed451 ms
14 days agoHandshake completed638 ms
15 days agoHandshake completed523 ms
16 days agoHandshake completed465 ms
17 days agoHandshake completed477 ms
18 days agoHandshake completed706 ms
19 days agoHandshake completed493 ms
22 days agoHandshake completed944 ms
25 days agoHandshake completed420 ms
27 days agoHandshake completed956 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 Mark and makes no claim about it beyond what these checks measured.