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.markovianprotocol.com/mcp/

The last check completed an MCP handshake.

Registry name
io.github.MarkovianProtocol/provenance
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
240 ms
Tools exposed
4 tools
Uptime, last 30 days
93.8% from 16 checks
Described by its publisher as
Stamp or notarize data into a public witnessed transparency log. Proves timing, not truth.
Listing
From the official MCP registry (active).
Recent checks of io.github.MarkovianProtocol/provenance
CheckedResultHandshake
1 hour agoHandshake completed240 ms
2 days agoHandshake completed282 ms
4 days agoHandshake completed215 ms
5 days agoHandshake completed221 ms
7 days agoHandshake completed255 ms
8 days agoHandshake completed664 ms
9 days agoHandshake completed227 ms
12 days agoHandshake completed254 ms
13 days agoHandshake completed263 ms
15 days agoHandshake completed196 ms
16 days agoHandshake completed281 ms
17 days agoHandshake completed312 ms
19 days agoHandshake completed256 ms
20 days agoHandshake completed255 ms
20 days agoHandshake completed231 ms
21 days agoFailed - the server returned an HTTP error—

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