Remote MCP · Endpoint

io.github.MarkovianProtocol/provenance MCP server

No. io.github.MarkovianProtocol/provenance answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.quantsynth.net/mcp/

The last check completed an MCP handshake.

Registry name
io.github.MarkovianProtocol/provenance
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
243 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Stamp any data to the Markovian chain for a verifiable provenance receipt. Proves timing, not truth.
Listing
From the official MCP registry (active).
Recent checks of io.github.MarkovianProtocol/provenance
CheckedResultHandshake
1 hour agoHandshake completed243 ms
1 day agoHandshake completed371 ms
2 days agoHandshake completed246 ms
3 days agoHandshake completed340 ms
4 days agoHandshake completed1.48 s
5 days agoHandshake completed220 ms
6 days agoHandshake completed302 ms
9 days agoHandshake completed258 ms
11 days agoHandshake completed1.56 s
14 days agoHandshake completed276 ms
16 days agoHandshake completed319 ms
18 days agoHandshake completed392 ms
20 days agoHandshake completed344 ms
22 days agoHandshake completed826 ms
24 days agoHandshake completed239 ms
26 days agoHandshake completed202 ms
27 days agoHandshake completed388 ms
29 days agoHandshake completed662 ms

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

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 io.github.MarkovianProtocol/provenance and makes no claim about it beyond what these checks measured.