# io.github.MarkovianProtocol/provenance (remote · api.markovianprotocol.com)

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

- Trust score: 60/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

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

## Channel facts

- Endpoint: `https://api.markovianprotocol.com/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.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-09-25.

- **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 enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - 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**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 830 tokens (~207/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 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 (25% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.MarkovianProtocol/provenance MCP server?

io.github.MarkovianProtocol/provenance is a hosted endpoint at https://api.markovianprotocol.com/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.

### Claude

```bash
claude mcp add --transport http markovianprotocol-provenance 'https://api.markovianprotocol.com/mcp/'
```

### Cursor

```json
{
  "mcpServers": {
    "markovianprotocol-provenance": {
      "url": "https://api.markovianprotocol.com/mcp/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "markovianprotocol-provenance": {
      "type": "http",
      "url": "https://api.markovianprotocol.com/mcp/"
    }
  }
}
```

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

```json
{
  "McpServers": {
    "markovianprotocol-provenance": {
      "Transport": "http",
      "Url": "https://api.markovianprotocol.com/mcp/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add markovianprotocol-provenance -t streamable-http -u 'https://api.markovianprotocol.com/mcp/'
```

### Other

```json
{
  "mcpServers": {
    "markovianprotocol-provenance": {
      "type": "http",
      "url": "https://api.markovianprotocol.com/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-09-25 (score 60, 0)

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

### 2026-09-24 (score 60)

First indexed and scored.

## MCP tools (4)

### `markovian_notarize` (~228 tokens)

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.

Input parameters:

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

### `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-2#diagnostics

## Score history

- 2026-09-25: 60
- 2026-09-24: 60

## Common questions

### 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 or notarize data into a public witnessed transparency log. Proves timing, not truth. This page covers its hosted endpoint (https://api.markovianprotocol.com/mcp/).

### Is the io.github.MarkovianProtocol/provenance MCP server safe to use?

io.github.MarkovianProtocol/provenance scores 60 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 830 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 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

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