mcpbeat Sign in

Provenance MCP Server

by markovianprotocol Your server? Claim it
answering

Provenance is answering right now. Last checked 5 min ago. It exposes 4 tools.

Stamp or notarize data into a public witnessed transparency log. Proves timing, not truth.

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

Uptime history 91 days of history · worst day 78%
91 days agonow
100.0%
Uptime 24h
182 of 182 checks
4
Tools
read from the server
636 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 3

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 13 August 2026. No other catalogue keeps this.

23 Sep a tool description was rewritten markovian_notarize
23 Sep a tool changed the parameters it asks for markovian_notarize
13 Aug a tool appeared markovian_notarize

Provenance missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add provenance --transport http https://api.quantsynth.net/mcp/
Settings → Connectors → Add custom connector, then paste this address
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
{
  "servers": {
    "provenance": {
      "type": "http",
      "url": "https://api.quantsynth.net/mcp/"
    }
  }
}

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 4

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

markovian
markovian_notarize
Notarize any file or hash into a public transparency log cosigned by 7 witnesses from 6 operators and anchored to Bitcoin. Hash-only: pass a sha256 hex string, or with the local stdio server a file path (hashed on your machine; the file never leaves it) — only 32 bytes reach the log. Returns a receipt with the leaf index, inclusion-proof URL, an offline c2sp.org/tlog-proof bundle URL, and the witness trust policy. Proves the hash existed no later than the covering checkpoint, in a single history everyone sees identically; does NOT prove authorship or that the content is true. Rate-limited (10/hour). Typical use: notarize an output the moment it is produced, keep the file, hand anyone the proof URL.
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

URLTransportStateLatencyChecked
https://api.quantsynth.net/mcp/ streamable-http answering 638 ms 5 min ago
https://api.markovianprotocol.com/mcp/ streamable-http answering 570 ms 5 min ago

Alternatives to Provenance

same job, measured the same way
Sigstore Rekor
by pipeworx-io

Sigstore Rekor — the public transparency log for software signatures.

184 installs/wk 48 tools answering
WeSupport-AI
by petros-poli

Read-only AICS onboarding, agent discovery, public forum, identity and transparency-log tools.

194 installs/wk local only
HISTOR — MCP tool-definition transparency log
by alexar76

Check, diff and history of MCP tool definitions, from a public signed log of 88k+ servers.

2 056 installs/wk local only
McpStamp Timer Tracking
by theluckystrike

Run a work timer, log hours per project and rate, and turn unbilled time into invoice lines.

20 tools answering
Emulo
by ohad6k

Mine your AI coding session logs into a you.md profile with dated receipts, for an agent to read.

124 installs/wk local only
Log Pii Telemetry Lint
by jmshinhwa

22 rules that name the lines where a Node or TypeScript service writes personal data into logs, cras

47 installs/wk local only
WormaCeptor
by wormaceptor

Inspect a running Android debug app: network traffic, crashes, logs, databases and preferences

182 installs/wk local only
I
Israel Gateway
by aihub1234

Live Israeli public data for AI agents: alerts, prices, open data, FX rates, Shabbat times.

10 tools answering

Provenance — questions

Answers built from our own checks of this server.

What can Provenance do?
It exposes 4 tools, read directly from the server on our last check. Among them: markovian_notarize, 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 182 of 182 checks got a reply (100.0%), average response time 636 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 in the form 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 4 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 636 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.