Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Proofestry

REMOTE · API.PROOFESTRY.DEV

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

+3 this week 66 Trust /100

Last scanned (16 hours ago)

Scores higher than 51% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 403, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 84% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 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. See how to fix → Fail
  • An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 403, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +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.

  • 18 Nov 26 +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.

  • 15 Nov 26 +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.

  • 13 Nov 26 +1
    • Tool “mark_content” rewrote its description, which is the text the model reads security
    • “mark_content” added an optional parameter “existing_credentials” cosmetic
  • 11 Nov 26 +1
    • 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 security
    • Stability: unverified → 0.03 ▲ functional
    • “compliance_report” added an optional parameter “cursor” cosmetic
    • “compliance_report” added an optional parameter “limit” cosmetic
  • 10 Nov 26 61

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://api.proofestry.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.proofestry.dev CN=Amazon RSA 2048 S25,O=Amazon,C=US 6 Nov 2026 23 May 2027 RSA 2048 SHA256-RSA 43c3b93d650a90ad621fb7a53715ac03
SANs: api.proofestry.dev
CN=Amazon RSA 2048 S25,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 8 Jul 2026 7 Jul 2029 RSA 2048 SHA256-RSA 77570e1c2927048b87b9ebb9e7bd025d20dd5b1f
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.proofestry.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
proofestry.dev. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.proofestry.dev/mcp Verified 200
http (plaintext) http://api.proofestry.dev/mcp Inconclusive 403
MCP tools · 15 exposed · ~2,273 tokens

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 →

Tool Tokens
check_redactions ~106

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`.

NameTypeReqDescription
file_base64stringyesBase64-encoded file bytes (max 4 MiB).

No output schema declared.

No examples provided.

clean_metadata ~165

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.

NameTypeReqDescription
file_base64stringyesBase64-encoded file bytes (max 4 MiB).

No output schema declared.

No examples provided.

compliance_report ~171

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`.

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

No output schema declared.

No examples provided.

detect_provenance ~187

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.

NameTypeReqDescription
file_base64stringyesBase64-encoded file bytes (max 4 MiB).

No output schema declared.

No examples provided.

list_compliance_profiles ~58

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`.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mark_content ~470

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.

NameTypeReqDescription
existing_credentialsstring–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_base64stringyesBase64-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>`.
profilestringyesCompliance profile (see GET /v1/provenance/profiles).
provider_namestring–Who provides the AI system. Required for the AI profiles.
source_type––provenance-only only: digitalCapture, digitalCreation, humanEdits or screenCapture (default digitalCreation).
strip_metadataboolean–Remove EXIF metadata (for example GPS) from the marked file.
system_namestring–The AI system that generated the content. Required for the AI profiles.
system_versionstring––
visible_labelboolean–Draw a visible 'AI-generated' label on the image (AI profiles only).

No output schema declared.

No examples provided.

request_missing_tool ~31

Free. MCP tool: `request_missing_tool`.

NameTypeReqDescription
descriptionstringyesThe tool you wish existed.

No output schema declared.

No examples provided.

scan_file ~168

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`.

NameTypeReqDescription
file_base64stringyesBase64-encoded file bytes (max 4 MiB).

No output schema declared.

No examples provided.

scan_metadata ~132

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.

NameTypeReqDescription
file_base64stringyesBase64-encoded file bytes (max 4 MiB).

No output schema declared.

No examples provided.

snapshot_citation ~231

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`.

NameTypeReqDescription
include_contentboolean–Also return the fetched bytes (base64, up to 1 MiB) so you can keep them. Proofestry never stores the content.
urlstringyesA public http(s) page, on port 80 or 443. Addresses on private networks are refused.

No output schema declared.

No examples provided.

snapshot_citations ~104

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`.

NameTypeReqDescription
include_contentboolean––
urlsarrayyesOne to five public http(s) URLs. All or nothing: if any fails, the call fails and is not charged.

No output schema declared.

No examples provided.

timestamp ~176

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`.

NameTypeReqDescription
labelstring–An optional note stored with the timestamp.
sha256stringyesThe SHA-256 of your content, as 64 hexadecimal characters. Only this hash is sent; Proofestry never sees the content.

No output schema declared.

No examples provided.

verify_provenance ~104

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`.

NameTypeReqDescription
file_base64stringyesBase64-encoded file bytes (max 4 MiB).

No output schema declared.

No examples provided.

verify_snapshot ~78

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`.

NameTypeReqDescription
idstringyes–
sha256––Optional: a content hash to compare with the recorded one.

No output schema declared.

No examples provided.

verify_timestamp ~92

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`.

NameTypeReqDescription
idstringyes–
sha256––Optional: a hash to compare with the timestamped one.

No output schema declared.

No examples provided.

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.

remote · api.proofestry.dev

# add to Claude Code
claude mcp add --transport http com-proofestry-proofestry 'https://api.proofestry.dev/mcp'
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.