# Orphograph (mcpb · orphograph-mcp-0.1.1.mcpb)

Anchor a file's SHA-256 fingerprint to Bitcoin. The file never leaves the device.

- Trust score: 45/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-22

## Components

- mcpb · `orphograph-mcp-0.1.1.mcpb`: 45/100 (this document), [markdown](https://verifymcp.io/servers/orphograph-orphograph/https-github-com-orphograph-orphograph-releases-download-mcp-v0-1-1-orphograph-m.md), [page](https://verifymcp.io/servers/orphograph-orphograph/https-github-com-orphograph-orphograph-releases-download-mcp-v0-1-1-orphograph-m)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/Orphograph/Orphograph/releases/download/mcp-v0.1.1/orphograph-mcp-0.1.1.mcpb`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-22.

- **Supply Chain Security**: 13/100
  - Malware scan not yet available for this package.
  - Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.
  - No install/post-install scripts declared.
  - Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 9 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 808 tokens (~134/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 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.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

- Download bundle: `https://github.com/Orphograph/Orphograph/releases/download/mcp-v0.1.1/orphograph-mcp-0.1.1.mcpb`

## 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-20 (score 45, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-08-12 (score 41)

First indexed and scored.

## MCP tools (6)

### `orphograph_anchor_file` (~144 tokens)

Anchor a local file to the Bitcoin chain via Orphograph. Reads the file locally, computes SHA-256 and SHA-512 in-process, and transmits ONLY those fingerprints. The file body never leaves the device. Returns a receipt id, a receipt URL, and calendar attestation counts.

Input parameters:

- `c2pa_manifest_hash` (string): Optional SHA-256 hex of a C2PA manifest the receipt should reference (coexistence mode).
- `label` (string): Optional human-readable label (max 200 chars). Stored on the receipt; do not include sensitive content.
- `path` (string, required): Absolute or relative path to the file to anchor.

### `orphograph_anchor_folder` (~137 tokens)

Anchor a whole folder (a dataset) to the Bitcoin chain via Orphograph. Every file is hashed locally into an RFC-6962 Merkle tree; ONLY the manifest (relative paths + SHA-256 digests + the root) is transmitted — no file body leaves the device. Returns a receipt id and a hosted certificate URL; each file stays independently verifiable via an inclusion proof.

Input parameters:

- `label` (string): Optional human-readable label (max 200 chars). Stored on the receipt; do not include sensitive content.
- `path` (string, required): Absolute or relative path to the folder (dataset bundle) to anchor.

### `orphograph_anchor_output` (~250 tokens)

Anchor a string of generated OUTPUT (an AI agent's result, a model response, a transcript, any text) to the Bitcoin chain — without writing a file first. Hashes the UTF-8 text in-process and transmits ONLY the SHA-256/512 fingerprints; the text never leaves the device. Use this to prove an exact output existed at a specific time. Returns a receipt id, a receipt URL, and calendar attestation counts.

Input parameters:

- `c2pa_manifest_hash` (string): Optional SHA-256 hex of a C2PA manifest the receipt should reference (coexistence mode).
- `label` (string): Optional human-readable label (max 200 chars). Stored on the receipt; do not include sensitive content.
- `text` (string, required): The output text to anchor. Hashed locally; not transmitted.
- `zk_proof` (object): Optional zero-knowledge execution proof, echoed on the receipt as zk_provenance. SCOPE, which a relaying agent should repeat: it proves a fixed, published hash-chain procedure ran — NOT that a specif…

### `orphograph_verify_receipt` (~129 tokens)

Look up an existing Orphograph receipt and return what the office recorded for it: the anchored hashes, the calendar attestation counts, and (when available) the time the pin to Bitcoin was OBSERVED. This reads the office's record — it does NOT independently verify the Bitcoin chain, and the observed pin time is not the block's own timestamp. For an independent chain check, run the OpenTimestamps client (`ots verify`) against the receipt's .ots files. Does not require an API key.

Input parameters:

- `receipt_id` (string, required): The receipt identifier issued at anchor time.

### `orphograph_verify_lineage` (~82 tokens)

Walk the parent links of a receipt's edit lineage and verify each link. Reports anchor-time ordering only — it does not assess content similarity, authorship, or whether siblings exist.

Input parameters:

- `max_depth` (integer): Maximum number of links to walk (1-256). Defaults to 32.
- `receipt_id` (string, required): tip receipt id

### `orphograph_list_vault` (~66 tokens)

List the signed-in subscriber's anchored receipts. Requires ORPHO_API_KEY in the environment. The key is issued from https://orphograph.com/account.html.

Input parameters:

- `limit` (integer): Maximum number of receipts to return (1-500). Defaults to 50.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/orphograph-orphograph/https-github-com-orphograph-orphograph-releases-download-mcp-v0-1-1-orphograph-m#diagnostics

## Score history

- 2026-08-22: 45
- 2026-08-21: 45
- 2026-08-20: 45
- 2026-08-19: 41
- 2026-08-18: 41
- 2026-08-17: 41
- 2026-08-16: 41
- 2026-08-15: 41
- 2026-08-14: 41
- 2026-08-13: 41
- 2026-08-12: 41

## Links

- Repository: https://github.com/Orphograph/Orphograph
- Website: https://orphograph.com/mcp.html
- Changelog RSS feed: https://verifymcp.io/servers/orphograph-orphograph/https-github-com-orphograph-orphograph-releases-download-mcp-v0-1-1-orphograph-m.xml
- Changelog JSON feed: https://verifymcp.io/servers/orphograph-orphograph/https-github-com-orphograph-orphograph-releases-download-mcp-v0-1-1-orphograph-m.json
- HTML version of this page: https://verifymcp.io/servers/orphograph-orphograph/https-github-com-orphograph-orphograph-releases-download-mcp-v0-1-1-orphograph-m