# io.github.MarkovianProtocol/provenance (remote · api.quantsynth.net)

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

- Trust score: 61/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.quantsynth.net`: 61/100 (this document), [markdown](https://verifymcp.io/servers/markovianprotocol-provenance/api.md), [page](https://verifymcp.io/servers/markovianprotocol-provenance/api)

## Channel facts

- Endpoint: `https://api.quantsynth.net/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 602 tokens (~200/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (33% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.markovianprotocol-provenance]
url = "https://api.quantsynth.net/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "markovianprotocol-provenance": {
      "type": "remote",
      "url": "https://api.quantsynth.net/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add markovianprotocol-provenance --url https://api.quantsynth.net/mcp/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  markovianprotocol-provenance:
    url: "https://api.quantsynth.net/mcp/"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 60, 0)

- [security] Tool “markovian_verify” rewrote its description, which is the text the model reads

### 2026-07-31 (score 60, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 61, 0)

- [security] Tool “markovian_stamp” rewrote its description, which is the text the model reads
- [cosmetic] “markovian_stamp” reworded the description of “wallet”

### 2026-07-29 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 59, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 59)

First indexed and scored.

## MCP tools (3)

### `markovian_stamp` (~318 tokens)

Markovian Provenance 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.

Input parameters:

- `data` (string, required): 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.

Output parameters:

- `attestation` (string)
- `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)
- `issuer` (string): The committer handle, as named in the transparency-log leaf. Attribution metadata, not a cryptographic identity.
- `merkle_root` (string)
- `schema` (string)
- `stamped_at` (string)
- `verify` (string)
- `wallet` (string): 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.

### `markovian_verify` (~157 tokens)

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.

Input parameters:

- `merkle_root` (string, required): merkle_root to verify.

### `markovian_trace` (~127 tokens)

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.

Input parameters:

- `merkle_root` (string, required): root of the stamp to trace.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/markovianprotocol-provenance/api#diagnostics

## Score history

- 2026-08-03: 61
- 2026-08-02: 60
- 2026-08-01: 60
- 2026-07-31: 60
- 2026-07-30: 61
- 2026-07-29: 61
- 2026-07-28: 60
- 2026-07-27: 59
- 2026-07-26: 59

## Links

- Remote endpoint: https://api.quantsynth.net/mcp/
- Repository: https://github.com/MarkovianProtocol/markovian-protocol
- Changelog RSS feed: https://verifymcp.io/servers/markovianprotocol-provenance/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/markovianprotocol-provenance/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/markovianprotocol-provenance/api