This MCP server provides a provenance and trust layer for autonomous agents by stamping data into a Markovian chain. It produces independently verifiable, timestamped receipts to prove commit timing, not data truth. The protocol is content-agnostic: agents submit a hash, and the system records cryptographic commitments on-chain.

🛠️ Key Features

Content-agnostic stamping by submitting a hash
On-chain recording of a Merkle root
BN128 Pedersen commitment written to the chain
Receipt returned for independent verification (no account required)

🚀 Use Cases

Verifiable provenance receipts for agent-generated outputs
Auditing when data was committed
Systems needing provenance, not claims of correctness

⚡ Developer Benefits

Anyone can verify receipts without trusting the issuer
Timing evidence suitable for provenance and trust workflows
Content-agnostic commit flow (hash in, receipt out)

⚠️ Limitations

Does not claim the underlying data is correct
Proves timing/commitment, not truth

Markovian Protocol

A provenance and trust layer for autonomous agents. The Markovian Protocol turns any agent output into a timestamped, chain-recorded, independently verifiable record. It proves that data was committed at a point in time. It does not claim the data is correct. Provenance, not truth.

COMMIT

COMMIT is the entrance. It is a content-agnostic stamp: an agent sends a hash, the protocol writes a Merkle root plus a BN128 Pedersen commitment to the chain, and returns a receipt that anyone can verify with no account and without trusting the issuer.

The canonical record is the same object everywhere, markovian-provenance/v1:

json

{
  "schema": "markovian-provenance/v1",
  "merkle_root": "<sha256(data_hash:salt:wallet)>",
  "data_hash": "<sha256 of the committed data>",
  "wallet": "<stamper wallet>",
  "zk_commitment": "<BN128 Pedersen point>",
  "block_height": 0,
  "stamped_at": "<timestamp>",
  "verify": "https://api.quantsynth.net/verify/<merkle_root>",
  "attestation": "provenance-only; proves data was committed at this time, not that it is correct"
}

Doors

One commit, many envelopes. The same record plugs into the standards agents already use.

Standard	Status	How it plugs in
W3C Verifiable Credentials	Live	The record becomes the credentialSubject of a signed VC
A2A, Agent2Agent	Live	A data-only extension attaches the record to Artifact.metadata
Model Context Protocol	Live	An MCP server exposes a stamp tool and a verify tool
ERC-8004, Trustless Agents	Testnet	A validation provider answers on the Validation Registry
C2PA	Planned	A namespaced assertion inside a content manifest

Reference pages for each door, with live examples:

W3C VC: https://markovianprotocol.com/vc.html
A2A: https://markovianprotocol.com/a2a.html
MCP: https://markovianprotocol.com/mcp.html
ERC-8004: https://markovianprotocol.com/erc8004.html

Try it

Stamp something and verify it in thirty seconds. No account, no wallet, no token.

bash

pip install markovian

python

from markovian import MarkovianClient

client = MarkovianClient()                 # free tier, no key
receipt = client.stamp("my agent predicted X at 09:00")
print(receipt["verify_url"])               # anyone can check this

client.verify(receipt["merkle_root"])      # {'verified': True, ...}

The record is committed to the chain before the outcome is known. That is the point. A track record that cannot be edited in hindsight. The basic stamp burns no MKV.

Now anyone confirms it, with no SDK and no account:

bash

curl https://api.quantsynth.net/verify/<merkle_root>

Same record, other doors:

bash

# MCP server (Streamable HTTP, trailing slash required)
# https://api.quantsynth.net/mcp/   tools: markovian_stamp, markovian_verify

# A2A extension definition
curl https://api.quantsynth.net/a2a/ext/provenance/v1

A real record, verifiable in the browser: https://demo.markovianprotocol.com

A runnable version of the loop above: examples/stamp_and_verify.py

The MCP server is listed in the official MCP registry as io.github.MarkovianProtocol/provenance.

This repository

integrations/mcp/ MCP server and test
integrations/a2a/ A2A reference implementation: wrapper, demo agent, demo consumer
integrations/erc8004/ ERC-8004 Validation Registry contract and agent demo
specs/ integration specifications for the MCP, A2A, and C2PA doors
chain code: block_schema.py, miner.py, zk_markov.py, market_settler.py, reader_settler.py
whitepaper.md

The live signal pipeline and the production API are operated privately. This repository holds the protocol primitive, the door integrations, and the specifications.

License

Apache-2.0. See LICENSE and NOTICE.

path	string	optional	Local stdio server only: file to notarize, hashed on your machine and never uploaded. The hosted server refuses it.
sha256	string	optional	Alternatively, a sha256 hex digest (with or without 'sha256:' prefix).

data	string	required	Exact bytes/string to stamp. Hashed server-side; raw data is not stored.
wallet	string	optional	Optional. Omit and the protocol mints an ephemeral committer for you. Provide one to attribute the stamp.
label	string	optional	Optional human label for the stamp.
derived_from	array	optional	Optional lineage. A list of prior stamps this output was derived from, each {merkle_root, data_hash}. Bound inside the committed bytes so the link is tamper-evident; the payload is published so markovian_trace can walk it.

io.github.MarkovianProtocol/provenance

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

markovian_notarize

markovian_stamp

markovian_verify

markovian_trace

Markovian Protocol

COMMIT

Doors

Try it

This repository

License

Install

Remote endpoint

Related servers