Server data from the Official MCP Registry
Stamp any data to the Markovian chain for a verifiable provenance receipt. Proves timing, not truth.
Stamp any data to the Markovian chain for a verifiable provenance receipt. Proves timing, not truth.
Remote endpoints: streamable-http: https://api.quantsynth.net/mcp/
The MCP server itself is well-structured with proper authentication delegated to wallet addresses and no direct code vulnerabilities. However, critical hardcoded credentials in backend settlement scripts (database passwords, API keys) and unauthenticated access to public endpoints create moderate risk. The codebase mixes provenance-layer infrastructure with financial settlement logic, and several scripts lack proper error handling for sensitive operations. Supply chain analysis found 4 known vulnerabilities in dependencies (1 critical, 3 high severity).
7 files analyzed · 18 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Available as Local & Remote
This plugin can run on your machine or connect to a hosted endpoint. during install.
From the project's GitHub README.
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 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:
{
"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"
}
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:
The doors are live. These calls run against the public endpoint, no account required.
# Verify any record (browser or API)
curl https://api.quantsynth.net/verify/<merkle_root>
# The MCP server (Streamable HTTP, trailing slash required)
# https://api.quantsynth.net/mcp/ tools: markovian_stamp, markovian_verify
# The A2A extension definition
curl https://api.quantsynth.net/a2a/ext/provenance/v1
A real record, verifiable in the browser: https://demo.markovianprotocol.com
The MCP server is listed in the official MCP registry as io.github.MarkovianProtocol/provenance.
integrations/mcp/ MCP server and testintegrations/a2a/ A2A reference implementation: wrapper, demo agent, demo consumerintegrations/erc8004/ ERC-8004 Validation Registry contract and agent demospecs/ integration specifications for the MCP, A2A, and C2PA doorsblock_schema.py, miner.py, zk_markov.py, market_settler.py, reader_settler.pywhitepaper.mdThe live signal pipeline and the production API are operated privately. This repository holds the protocol primitive, the door integrations, and the specifications.
Apache-2.0. See LICENSE and NOTICE.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.