Orphograph
MCPB · ORPHOGRAPH-MCP-0.1.1.MCPB · SCANNED AUG 22
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 →
Supply Chain Security13
- Malware scan not yet available for this package.Unverified
- 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.Unverified
- No install/post-install scripts declared.Pass
- 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.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 9 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 Management33
- Stability observed for 10 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
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
mcpb · orphograph-mcp-0.1.1.mcpb
Download bundleEvery 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.
- 20 Aug 26 +4
- Stability: unverified → 0.27 ▲ functional
- 12 Aug 26 41
First indexed and scored.
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 22 Aug 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 |
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.
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.