# Proofestry (remote · api.proofestry.dev)

Provenance and metadata tools for AI agents. Paid tools use x402 (USDC) at /mcp/<tool>.

- Trust score: 66/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `api.proofestry.dev`: 66/100 (this document), [markdown](https://verifymcp.io/servers/com-proofestry-proofestry/api.md), [page](https://verifymcp.io/servers/com-proofestry-proofestry/api)

## Channel facts

- Endpoint: `https://api.proofestry.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 403, 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**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2313 tokens (~154/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 84% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "clean_metadata" implies "remove" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Proofestry MCP server?

Proofestry is a hosted endpoint at https://api.proofestry.dev/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 com-proofestry-proofestry 'https://api.proofestry.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-proofestry-proofestry": {
      "url": "https://api.proofestry.dev/mcp"
    }
  }
}
```

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-proofestry-proofestry:
    url: "https://api.proofestry.dev/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-proofestry-proofestry": {
      "type": "http",
      "url": "https://api.proofestry.dev/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-11-20 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 63, +1)

- [security] Tool “mark_content” rewrote its description, which is the text the model reads
- [cosmetic] “mark_content” added an optional parameter “existing_credentials”

### 2026-11-11 (score 62, +1)

- [security] Tool “compliance_report” rewrote its description, which is the text the model reads
- [security] Tool “detect_provenance” rewrote its description, which is the text the model reads
- [security] Tool “mark_content” rewrote its description, which is the text the model reads
- [security] Tool “scan_metadata” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “compliance_report” added an optional parameter “cursor”
- [cosmetic] “compliance_report” added an optional parameter “limit”

### 2026-11-10 (score 61)

First indexed and scored.

## MCP tools (15)

### `scan_metadata` (~132 tokens)

Scan a file's metadata for privacy risks

Lists EXIF, XMP and PNG text metadata with a risk rating. Inspects JPEG, PNG, HEIC/HEIF, WebP, TIFF, AVIF, MP4/QuickTime, AVI, Matroska and WebM video (container metadata only). Any other format returns `supported: false` and `overall_risk: unknown`: nothing was inspected, so no findings does not mean no metadata. MCP tool: `scan_metadata`. Price: 0.002 USDC per file.

Input parameters:

- `file_base64` (string, required): Base64-encoded file bytes (max 4 MiB).

### `detect_provenance` (~187 tokens)

Detect provenance and AI-generation signals

Reads and validates C2PA manifests (signature and hashes), IPTC DigitalSourceType, and generator metadata. Flags stripped, invalid or conflicting credentials. Reports signals and confidence, never a definitive 'not AI-generated'; the C2PA signer is not yet checked against the trust list. C2PA manifests are read and validated in images, PDF, Office and OpenDocument files, audio and video (see supported-formats.json). IPTC, XMP, EXIF and generator-name signals are read for JPEG, PNG, HEIC/HEIF, WebP, TIFF, AVIF and MP4/QuickTime; `checks_run` says what ran for each file. MCP tool: `detect_provenance`. Price: 0.002 USDC per image.

Input parameters:

- `file_base64` (string, required): Base64-encoded file bytes (max 4 MiB).

### `mark_content` (~470 tokens)

Apply a compliance profile to an image

Marks an AI-generated or human-made image with a compliance profile: a signed C2PA manifest with the profile's disclosure, an invisible watermark (the AI profiles), an ISCC fingerprint registered with Proofestry, and a trusted timestamp when the signing provider has one. Returns the marked file (base64 in the REST response; a short-lived download link over MCP). Marking the same image again is idempotent: it returns the same asset id and never creates a second record. Profiles help meet obligations and do not guarantee compliance; they are in beta until the signer is on the C2PA trust list. An image that already carries Content Credentials is kept as the parent of the new manifest (existing_credentials=reject refuses it). Images up to 1 MiB inline (JPEG, PNG, WebP, HEIC); larger files use the upload job routes. Failed calls are never charged. MCP tool: `mark_content`. Price: 0.01 USDC per image.

Input parameters:

- `existing_credentials` (string): What to do with an image that already carries Content Credentials: `preserve` (default) keeps them as the parent of the new manifest, so their history and signature stay in the file; `reject` refuses…
- `file_base64` (string, required): Base64-encoded file bytes (max 4 MiB).
- `invisible_watermark`: provenance-only: also embed the invisible watermark. The AI profiles always do.
- `ledger_id`: Add the asset to this ledger for the compliance report. Needs `Authorization: Bearer <ledger token>`.
- `profile` (string, required): Compliance profile (see GET /v1/provenance/profiles).
- `provider_name` (string): Who provides the AI system. Required for the AI profiles.
- `source_type`: provenance-only only: digitalCapture, digitalCreation, humanEdits or screenCapture (default digitalCreation).
- `strip_metadata` (boolean): Remove EXIF metadata (for example GPS) from the marked file.
- `system_name` (string): The AI system that generated the content. Required for the AI profiles.
- `system_version` (string)
- `visible_label` (boolean): Draw a visible 'AI-generated' label on the image (AI profiles only).

### `clean_metadata` (~165 tokens)

Remove private metadata from an image and return the cleaned copy

Removes EXIF (GPS, device, timestamps), XMP, IPTC and text metadata from a JPEG, PNG or WebP and returns the cleaned file, with a list of what was removed and what was kept (the picture, the color profile, the display orientation and the IPTC digital source type). The pixels are not re-encoded. A file that carries Content Credentials (C2PA) is refused with 409, since cleaning it would break their signature. Images up to 1 MiB inline; larger files use the upload job routes. Failed calls are never charged. MCP tool: `clean_metadata`. Price: 0.01 USDC per file.

Input parameters:

- `file_base64` (string, required): Base64-encoded file bytes (max 4 MiB).

### `scan_file` (~168 tokens)

Scan a file for hidden content, active content and prompt-injection text

Looks inside a PDF, Word, Excel or PowerPoint file, an image or a text/HTML file for what a reader does not see: scripts and launch actions, hidden or invisible text, embedded files, trailing data, and phrases that try to instruct an AI that reads the file. Reports each finding's kind, severity and location; for an injection phrase it quotes only the matched phrase (up to 80 characters), never other content. Not an antivirus and not a guarantee: `checks_run` lists what was inspected, and a file type with no checks returns `overall_risk: unknown`. Price: 0.01 USDC per file. MCP tool: `scan_file`.

Input parameters:

- `file_base64` (string, required): Base64-encoded file bytes (max 4 MiB).

### `check_redactions` (~106 tokens)

Check a PDF for redactions that did not remove the text

Finds black boxes drawn over text in a PDF and reports where the text underneath can still be selected or copied, and redaction annotations that were never applied. Returns locations and counts, never the hidden text. Checks text only: it does not look at images, metadata or earlier revisions. Price: 0.01 USDC per PDF. MCP tool: `check_redactions`.

Input parameters:

- `file_base64` (string, required): Base64-encoded file bytes (max 4 MiB).

### `list_compliance_profiles` (~58 tokens)

List compliance profiles

Free. The compliance profiles `mark_content` can apply, the layers each uses, the regulatory basis, and whether they are beta (until the signer is on the C2PA trust list). MCP tool: `list_compliance_profiles`.

### `verify_provenance` (~104 tokens)

Check whether a file is marked by Proofestry

Free. Checks a file for Proofestry's marks: the C2PA manifest (validated against Proofestry's records), the invisible watermark, and an exact fingerprint of files Proofestry delivered. Reports what was found; not finding marks never means a file is unmarked. Up to 4 MiB. MCP tool: `verify_provenance`.

Input parameters:

- `file_base64` (string, required): Base64-encoded file bytes (max 4 MiB).

### `compliance_report` (~171 tokens)

Compliance report for a ledger

An audit record of what was marked, when, with which layers and standard versions, for one ledger. Counts unique assets (a retry never adds one). Up to 5,000 assets per call: a larger ledger returns `next_cursor`, and each further page is a separate call and charge. Requires `Authorization: Bearer <ledger token>`; unknown ledgers and wrong tokens get the same 404, which is not charged. Price: 0.10 USDC. MCP tool: `compliance_report`.

Input parameters:

- `cursor`: Continue a large ledger: the `next_cursor` of the previous page. Omit for the first page.
- `ledger_id` (string, required)
- `limit`: Assets in this page (default and maximum 5,000). Each call is one priced report.

### `timestamp` (~176 tokens)

Timestamp a hash

Obtains an RFC 3161 timestamp token for a SHA-256 hash from a public timestamp authority and stores it, so the hash can be shown to have existed at that time. Only the hash is sent: Proofestry never sees the content. Returns the token (verifiable with `openssl ts -verify`) and a record id. A timestamp proves the hash existed then, not who made the content or that it is true. A failure at the authority is a 5xx and is never charged. Price: 0.01 USDC per hash. MCP tool: `timestamp`.

Input parameters:

- `label` (string): An optional note stored with the timestamp.
- `sha256` (string, required): The SHA-256 of your content, as 64 hexadecimal characters. Only this hash is sent; Proofestry never sees the content.

### `verify_timestamp` (~92 tokens)

Verify a timestamp

Free. Re-checks a stored timestamp: the authority's signature over the token, that it covers the recorded hash, and optionally that a hash you supply matches. Lists each check with its result; the authority's certificate chain is not evaluated against a trust list. MCP tool: `verify_timestamp`.

Input parameters:

- `id` (string, required)
- `sha256`: Optional: a hash to compare with the timestamped one.

### `snapshot_citation` (~231 tokens)

Snapshot a citation

Fetches a public web page and records what it served: the final URL, the time, the HTTP status, the content type, the SHA-256 of the bytes and the title. The record is timestamped (RFC 3161) and gets a permanent proof link. Proofestry does not store the page; set `include_content` to get the bytes back to keep. Only public http(s) pages on ports 80 and 443 are fetched; pages that need a login or JavaScript are captured as served to a plain request. A page that cannot be fetched, or answers with an error status, is a 4xx/5xx and is never charged. Price: 0.02 USDC per URL. MCP tool: `snapshot_citation`.

Input parameters:

- `include_content` (boolean): Also return the fetched bytes (base64, up to 1 MiB) so you can keep them. Proofestry never stores the content.
- `url` (string, required): A public http(s) page, on port 80 or 443. Addresses on private networks are refused.

### `snapshot_citations` (~104 tokens)

Snapshot up to five citations

Like `snapshot_citation` for one to five URLs in a single call, fetched in parallel. All or nothing: if any URL fails, the call fails and nothing is charged. Price: 0.075 USDC per batch. MCP tool: `snapshot_citations`.

Input parameters:

- `include_content` (boolean)
- `urls` (array, required): One to five public http(s) URLs. All or nothing: if any fails, the call fails and is not charged.

### `verify_snapshot` (~78 tokens)

Verify a snapshot

Free. Re-checks a stored snapshot: that its fields still hash to the timestamped record, the timestamp authority's signature, and optionally that a content hash you supply is the recorded one. MCP tool: `verify_snapshot`.

Input parameters:

- `id` (string, required)
- `sha256`: Optional: a content hash to compare with the recorded one.

### `request_missing_tool` (~31 tokens)

Request a missing tool

Free. MCP tool: `request_missing_tool`.

Input parameters:

- `description` (string, required): The tool you wish existed.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-proofestry-proofestry/api#diagnostics

## Score history

- 2026-11-21: 66
- 2026-11-20: 66
- 2026-11-19: 65
- 2026-11-18: 65
- 2026-11-17: 64
- 2026-11-16: 64
- 2026-11-15: 64
- 2026-11-14: 63
- 2026-11-13: 63
- 2026-11-12: 62
- 2026-11-11: 62
- 2026-11-10: 61

## Common questions

### What is the Proofestry MCP server?

Proofestry is an MCP server listed in the public MCP registry as com.proofestry/proofestry. Provenance and metadata tools for AI agents. Paid tools use x402 (USDC) at /mcp/<tool>. This page covers its hosted endpoint (https://api.proofestry.dev/mcp).

### Is the Proofestry MCP server safe to use?

Proofestry scores 66 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 Proofestry MCP server expose?

Proofestry exposes 15 tools: scan_metadata, detect_provenance, mark_content, clean_metadata, scan_file, and 10 more. Their descriptions and schemas cost roughly 2,273 tokens of context every time the server is loaded.

### Does the Proofestry MCP server require authentication?

No. We connected to Proofestry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Proofestry MCP server still maintained?

Proofestry is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Proofestry MCP server?

VerifyMCP ran 12 checks on Proofestry, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Proofestry: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.proofestry.dev/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-proofestry-proofestry/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-proofestry-proofestry/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-proofestry-proofestry/api.json
- HTML version of this page: https://verifymcp.io/servers/com-proofestry-proofestry/api
