Local MCP capabilities provider for Expo
Nothing to run from here
Proofestry is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
15
tools declared
remote
at its publisher
—
calls last 7d
What it does
Provenance and metadata tools for AI agents. Paid tools use x402 (USDC) at /mcp/.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http proofestry-mcp https://api.proofestry.dev/mcp
# 2 — ask your agent for something these tools do
# scan_metadata, detect_provenance, mark_content and 12 more
Proofestry costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PRAll 1 server
proofestry1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http proofestry-mcp https://api.proofestry.dev/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
15 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Lists EXIF, XMP and PNG text metadata with a risk rating. Inspects JPEG, PNG, HEIC/HEIF, WebP, TIFF and AVIF. 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_base64 | string | yes | Base64-encoded file bytes (max 4 MiB). |
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 suppo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_base64 | string | yes | Base64-encoded file bytes (max 4 MiB). |
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 ide
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_base64 | string | yes | Base64-encoded file bytes (max 4 MiB). |
| profile | string | yes | Compliance profile (see GET /v1/provenance/profiles). |
| provider_name | string | no | Who provides the AI system. Required for the AI profiles. |
| system_name | string | no | The AI system that generated the content. Required for the AI profiles. |
| system_version | string | no | — |
| source_type | no | provenance-only only: digitalCapture, digitalCreation, humanEdits or screenCapture (default digitalCreation). | |
| visible_label | boolean | no | Draw a visible 'AI-generated' label on the image (AI profiles only). |
| invisible_watermark | no | provenance-only: also embed the invisible watermark. The AI profiles always do. | |
| strip_metadata | boolean | no | Remove EXIF metadata (for example GPS) from the marked file. |
| ledger_id | no | Add the asset to this ledger for the compliance report. Needs Authorization: Bearer <ledger token>. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_base64 | string | yes | Base64-encoded file bytes (max 4 MiB). |
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 oth
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_base64 | string | yes | Base64-encoded file bytes (max 4 MiB). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_base64 | string | yes | Base64-encoded file bytes (max 4 MiB). |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_base64 | string | yes | Base64-encoded file bytes (max 4 MiB). |
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). 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ledger_id | string | yes | — |
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 autho
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sha256 | string | yes | The SHA-256 of your content, as 64 hexadecimal characters. Only this hash is sent; Proofestry never sees the content. |
| label | string | no | An optional note stored with the 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | — |
| sha256 | no | Optional: a hash to compare with the timestamped one. |
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 J
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | A public http(s) page, on port 80 or 443. Addresses on private networks are refused. |
| include_content | boolean | no | Also return the fetched bytes (base64, up to 1 MiB) so you can keep them. Proofestry never stores the content. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| urls | array | yes | One to five public http(s) URLs. All or nothing: if any fails, the call fails and is not charged. |
| include_content | boolean | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | — |
| sha256 | no | Optional: a content hash to compare with the recorded one. |
Free. MCP tool: request_missing_tool.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| description | string | yes | The tool you wish existed. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Proofestry or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 0.1.0 · scanned 10 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 2 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestd0db40868119d9ec9bfb2f15649a7a4b329f334a9d72f78e08df9e59ed17c8d9
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| scan_metadata | no tags | |
| detect_provenance | no tags | |
| mark_content | untrusted-inputstate-write | untrusted-input: keyword "download"; state-write: declares readOnlyHint: false |
| clean_metadata | no tags | |
| scan_file | no tags | |
| check_redactions | no tags | |
| list_compliance_profiles | no tags | |
| verify_provenance | no tags | |
| compliance_report | no tags | |
| timestamp | state-write | state-write: declares readOnlyHint: false |
| verify_timestamp | no tags | |
| snapshot_citation | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| snapshot_citations | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| verify_snapshot | no tags | |
| request_missing_tool | state-write | state-write: declares readOnlyHint: false |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digestd0db40868119d9ec
Scanned2026-11-10
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Proofestry can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.