Orphograph
MCPB · ORPHOGRAPH-MCP-0.1.1.MCPB · SCANNED OCT 7
Anchor a file's SHA-256 fingerprint to Bitcoin. The file never leaves the device.
Available components
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. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 55 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the Orphograph MCP server?
Orphograph ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check the download against.
mcpb · orphograph-mcp-0.1.1.mcpb
Download bundleThe MCP registry declares no SHA-256 for this bundle, so there is no published digest to check it against. Open it with an MCPB-capable host such as Claude Desktop.
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.
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 90. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 −3
- Stability: pass → 0.80 functional
- 3 Oct 26 +1
- Stability: 0.97 → pass security
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 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
- 26 Sept 26 −3
- Stability: pass → 0.77 functional
- 25 Sept 26 −3
- 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 8 Oct 2026 · Analysed mcpb/https://github.com/Orphograph/Orphograph/releases/download/mcp-v0.1.1/orphograph-mcp-0.1.1.mcpb@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
orphograph_anchor_file ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Absolute or relative path to the file to anchor. |
No output schema declared.
No examples provided.
orphograph_anchor_folder ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | – | Optional human-readable label (max 200 chars). Stored on the receipt; do not include sensitive content. |
| path | string | yes | Absolute or relative path to the folder (dataset bundle) to anchor. |
No output schema declared.
No examples provided.
orphograph_anchor_output ~250
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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… |
No output schema declared.
No examples provided.
orphograph_list_vault ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of receipts to return (1-500). Defaults to 50. |
No output schema declared.
No examples provided.
orphograph_verify_lineage ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| max_depth | integer | – | Maximum number of links to walk (1-256). Defaults to 32. |
| receipt_id | string | yes | tip receipt id |
No output schema declared.
No examples provided.
orphograph_verify_receipt ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt_id | string | yes | The receipt identifier issued at anchor time. |
No output schema declared.
No examples provided.
What is the Orphograph MCP server?
Orphograph is an MCP server listed in the public MCP registry as io.github.Orphograph/orphograph. Anchor a file's SHA-256 fingerprint to Bitcoin. The file never leaves the device. This page covers its MCPB bundle (https://github.com/Orphograph/Orphograph/releases/download/mcp-v0.1.1/orphograph-mcp-0.1.1.mcpb).
Is the Orphograph MCP server safe to use?
Orphograph scores 51 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 Orphograph MCP server expose?
Orphograph exposes 6 tools: orphograph_anchor_file, orphograph_anchor_folder, orphograph_anchor_output, orphograph_verify_receipt, orphograph_verify_lineage, orphograph_list_vault. Their descriptions and schemas cost roughly 808 tokens of context every time the server is loaded.
What licence is the Orphograph MCP server under?
Orphograph declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.