Remote MCP · Endpoint

Mark MCP server

No. Mark answered an MCP handshake 17 minutes ago.

UpLast checked 17 minutes ago

Server URL

https://mark.tatastu.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.tatastu/proof
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
379 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Mark: stamp files with a signed, timestamped provenance record. Hash locally; verify free.
Website
https://mark.tatastu.dev/
Listing
From the official MCP registry (active).
Recent checks of Mark
CheckedResultHandshake
17 minutes agoHandshake completed379 ms
9 days agoHandshake completed997 ms
9 days agoHandshake completed551 ms
11 days agoHandshake completed410 ms
12 days agoHandshake completed810 ms
13 days agoHandshake completed667 ms
14 days agoHandshake completed898 ms
14 days agoHandshake completed834 ms
16 days agoHandshake completed378 ms
19 days agoHandshake completed961 ms
21 days agoHandshake completed398 ms
24 days agoHandshake completed755 ms
26 days agoHandshake completed378 ms
28 days agoHandshake completed452 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.