Provenance MCP Server

io.github.MarkovianProtocol/provenance

answering

Provenance is answering right now. Last checked 13 min ago. It exposes 3 tools.

Stamp any data to the Markovian chain for a verifiable provenance receipt. Proves timing, not truth.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 40 hours of history

40 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

599 ms

Response time

average over 24h

open, no key

Access

streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add provenance --transport http https://api.quantsynth.net/mcp/

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "provenance": {
      "url": "https://api.quantsynth.net/mcp/"
    }
  }
}

~/.codex/config.toml

[mcp_servers.provenance]
url = "https://api.quantsynth.net/mcp/"

.cursor/mcp.json

{
  "mcpServers": {
    "provenance": {
      "url": "https://api.quantsynth.net/mcp/"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "provenance": {
      "url": "https://api.quantsynth.net/mcp/"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

markovian

markovian_stamp

Commit any data (an AI output, a decision, a record) into a public, witnessed transparency log and get back a verifiable, tamper-evident provenance stamp (canonical markovian-provenance/v1). It proves the data existed and was committed at this time; it does NOT assert the data is correct (provenance, not truth). No wallet, account, or funding is required, the first stamp just works, and only the SHA-256 hash of your data is sent to the public API, the raw data is never stored. The returned merkle_root is the handle: save it, then call markovian_verify(merkle_root) to prove integrity later, or pass prior stamps in derived_from to build a lineage you can walk with markovian_trace. Typical use: stamp an agent output the moment it is produced, so anyone can later confirm it was not altered.

markovian_trace

Walk and verify a stamp's full provenance lineage by merkle_root. Use this when a stamp was created with derived_from links, to map what an output was built from. Returns a MAP of the graph (not a yes/no verdict): each node carries hash_binds and anchored, each edge carries edge_verified, and `valid` is true only if every node and edge checks out. A node whose payload was never published is an unresolved frontier (resolved:false). Read-only. Provenance, not truth.

markovian_verify

Look up a Markovian stamp by its merkle_root against the public verifier, with no key or account. verified:true means the stamp record exists and the response echoes its committed data_hash — recompute your content's SHA-256 and compare it to that data_hash yourself to confirm the content is unaltered. An unknown merkle_root returns verified:false. The trust-nobody path is the stamp's witnessed transparency-log leaf (log_index / inclusion URL from markovian_stamp): its inclusion proof verifies against the witnessed log head with no trust in this endpoint. Read-only; anyone can run it, including a party who does not trust the stamper.

Endpoints

URL	Transport	State	Latency	Checked
https://api.quantsynth.net/mcp/	streamable-http	answering	627 ms	13 min ago

Provenance — questions

Answers built from our own checks of this server.

What can Provenance do?

It exposes 3 tools, read directly from the server on our last check. Among them: markovian_stamp, markovian_trace, markovian_verify. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Provenance working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 599 ms. The bar chart above shows every period we have measured.

Is Provenance still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

How do I connect Provenance?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Provenance need an API key?

No. Provenance completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Provenance?

It answers our handshake in 599 ms on average, which is faster than 16% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.