Markproof
NPM · MARKPROOF-MCP
Watermark and C2PA-sign AI-generated images and audio for EU AI Act Article 50, and verify files.
Available components
Last scanned (5 hours ago)
Scores higher than 35% of npm servers
Category Security
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- 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 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 474 tokens (~158/item across 3 items; 3 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 Management13
- Stability observed for 4 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Security disclosure: unverified → fail ▼ functional
- Package version: 0.3.2 → 0.3.3 functional
- 3 Nov 26 +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.
- 1 Nov 26 65
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 5 Nov 2026 · Analysed npm/markproof-mcp@0.3.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_asset Look up a marked file ~49
Fetches the record for a file this account marked, by the asset_id that mark_file returned. Doesn't count toward the quota.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | yes | The asset_id returned by mark_file. |
No output schema declared.
No examples provided.
mark_file Mark an AI-generated file ~281
Adds an invisible watermark and a signed C2PA manifest (Content Credentials) to an AI-generated image (PNG, JPEG, WebP) or audio file (WAV, MP3), marking it as AI-generated for EU AI Act Article 50. Writes the marked copy next to the original (images as PNG, audio as WAV) and returns its watermark code and public verification URL. Use this on every image or audio file you generate before handing it to a user. Counts as one API call.
| Name | Type | Req | Description |
|---|---|---|---|
| generator_name | string | – | Name of the app or system that generated the file; recorded in the C2PA manifest. |
| label_position | string | – | Corner for visible_label. Defaults to bottom-right. |
| model_name | string | – | Name of the model that generated the file. |
| output_path | string | – | Where to write the marked copy. Defaults to <name>.marked.<ext> beside the original. |
| overwrite | boolean | – | Allow replacing an existing file at output_path. Defaults to false. |
| path | string | yes | Path to the local image or audio file to mark. |
| visible_label | – | – | Images only. Also draw a visible label on the image (EU AI Act Art. 50(4), e.g. for deepfakes): true for "AI-generated", or custom text up to 40 characters. |
No output schema declared.
No examples provided.
verify_file Check a file for AI marking ~144
Checks an image or audio file for a Markproof watermark and a C2PA manifest, and reports whether its signature is valid and whether it matches a record in this Markproof account. Use it to confirm a file is marked before publishing, or to inspect a file of unknown origin. Counts as one API call.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Path to the local image or audio file to check. Uploads are limited to about 4.5 MB. |
| url | string | – | Public https URL of the file, instead of path. Use it for files over 4.5 MB (up to 25 MB), e.g. marked audio, which is WAV. |
No output schema declared.
No examples provided.
How do I install the Markproof MCP server?
Markproof runs locally as an npm package, launched with npx -y markproof-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · markproof-mcp
claude mcp add ajinkya710-markproof -- npx -y markproof-mcp
What is the Markproof MCP server?
Markproof is an MCP server listed in the public MCP registry as io.github.Ajinkya710/markproof. Watermark and C2PA-sign AI-generated images and audio for EU AI Act Article 50, and verify files. This page covers its npm package (markproof-mcp).
Is the Markproof MCP server safe to use?
Markproof scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 Markproof MCP server expose?
Markproof exposes 3 tools: mark_file, verify_file, get_asset. Their descriptions and schemas cost roughly 474 tokens of context every time the server is loaded.
Is the Markproof MCP server still maintained?
Markproof is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Markproof MCP server under?
Markproof declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.