io.github.MarkovianProtocol/provenance
REMOTE · API.QUANTSYNTH.NET · SCANNED SEP 20
Stamp any data to the Markovian chain for a verifiable provenance receipt. Proves timing, not truth.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 809 tokens (~202/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (25% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.MarkovianProtocol/provenance MCP server?
io.github.MarkovianProtocol/provenance is a hosted endpoint at https://api.quantsynth.net/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.quantsynth.net
claude mcp add --transport http markovianprotocol-provenance 'https://api.quantsynth.net/mcp/'
{
"mcpServers": {
"markovianprotocol-provenance": {
"url": "https://api.quantsynth.net/mcp/"
}
}
} {
"servers": {
"markovianprotocol-provenance": {
"type": "http",
"url": "https://api.quantsynth.net/mcp/"
}
}
} [mcp_servers.markovianprotocol-provenance] url = "https://api.quantsynth.net/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"markovianprotocol-provenance": {
"type": "remote",
"url": "https://api.quantsynth.net/mcp/",
"enabled": true
}
}
} openclaw mcp add markovianprotocol-provenance --url 'https://api.quantsynth.net/mcp/' --transport streamable-http
mcp_servers:
markovianprotocol-provenance:
url: "https://api.quantsynth.net/mcp/" {
"McpServers": {
"markovianprotocol-provenance": {
"Transport": "http",
"Url": "https://api.quantsynth.net/mcp/"
}
}
} assistant mcp add markovianprotocol-provenance -t streamable-http -u 'https://api.quantsynth.net/mcp/'
{
"mcpServers": {
"markovianprotocol-provenance": {
"type": "http",
"url": "https://api.quantsynth.net/mcp/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Aug 26 0
- Tool coverage: 33% → 25% ▼ functional
- Schema quality: 602 → 809 ▼ functional
- New tool “markovian_notarize” functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 1 Aug 26 0
- Tool “markovian_verify” rewrote its description, which is the text the model reads security
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://api.quantsynth.net/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=quantsynth.net | CN=YE2,O=Let's Encrypt,C=US | 4 Sept 2026 | 3 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6e049a1bbcc897ac591a7cb35dac2d3fa10 |
| SANs: *.quantsynth.net, quantsynth.net | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.quantsynth.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| quantsynth.net. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.quantsynth.net/mcp/ | Verified | 200 | |
| http (plaintext) | http://api.quantsynth.net/mcp/ | Inconclusive | 406 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
markovian_notarize Markovian Notarize ~207
Notarize any file or hash into a public transparency log cosigned by 7 independent witnesses and anchored to Bitcoin. Hash-only: pass a local file path (hashed on this machine; the file never leaves it) or a sha256 hex string — 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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Local file to notarize. Hashed here; never uploaded. |
| sha256 | string | – | Alternatively, a sha256 hex digest (with or without 'sha256:' prefix). |
No output schema declared.
No examples provided.
markovian_stamp Markovian Provenance Stamp ~318
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.
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | yes | Exact bytes/string to stamp. Hashed server-side; raw data is not stored. |
| derived_from | array | – | 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 marko… |
| label | string | – | Optional human label for the stamp. |
| wallet | string | – | Optional. Omit and the protocol mints an ephemeral committer for you. Provide one to attribute the stamp. |
| Name | Type | Req | Description |
|---|---|---|---|
| attestation | string | yes | – |
| block_height | integer|null | – | Legacy field, null for stamps after 2026-07. Historical values are internal sequence heights of a retired chain (never a Bitcoin block). |
| data_hash | string | yes | – |
| issuer | string | – | The committer handle, as named in the transparency-log leaf. Attribution metadata, not a cryptographic identity. |
| merkle_root | string | yes | – |
| schema | string | yes | – |
| stamped_at | string | yes | – |
| verify | string | yes | – |
| wallet | string | yes | Compatibility alias for issuer (kept because existing clients require it). |
| zk_commitment | string|null | – | Legacy field, null for stamps after 2026-07. Historical values are Pedersen points that shipped without an opening, so clients could never check them. |
No examples provided.
markovian_trace Markovian Trace ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| merkle_root | string | yes | root of the stamp to trace. |
No output schema declared.
No examples provided.
markovian_verify Markovian Verify ~157
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.
| Name | Type | Req | Description |
|---|---|---|---|
| merkle_root | string | yes | merkle_root to verify. |
No output schema declared.
No examples provided.
What is the io.github.MarkovianProtocol/provenance MCP server?
io.github.MarkovianProtocol/provenance is an MCP server listed in the public MCP registry as io.github.MarkovianProtocol/provenance. Stamp any data to the Markovian chain for a verifiable provenance receipt. Proves timing, not truth. This page covers its hosted endpoint (https://api.quantsynth.net/mcp/).
Is the io.github.MarkovianProtocol/provenance MCP server safe to use?
io.github.MarkovianProtocol/provenance scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.MarkovianProtocol/provenance MCP server expose?
io.github.MarkovianProtocol/provenance exposes 4 tools: markovian_notarize, markovian_stamp, markovian_verify, markovian_trace. Their descriptions and schemas cost roughly 809 tokens of context every time the server is loaded.
Does the io.github.MarkovianProtocol/provenance MCP server require authentication?
No. We connected to io.github.MarkovianProtocol/provenance without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.MarkovianProtocol/provenance MCP server still maintained?
io.github.MarkovianProtocol/provenance is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.