ProofX - Content Protection for Creators
REMOTE · PROOFX-MCP.FLY.DEV · SCANNED SEP 20
Protect and verify digital content with cryptographic signing and proof of ownership.
Available components
Recent critical change
Authorization (18 Aug 2026). See the changelog before you install this server.
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
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (protect_content). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 408 tokens (~68/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
How do I install the ProofX - Content Protection for Creators MCP server?
ProofX - Content Protection for Creators is a hosted endpoint at https://proofx-mcp.fly.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 · proofx-mcp.fly.dev
claude mcp add --transport http razashariff-proofx 'https://proofx-mcp.fly.dev/mcp'
{
"mcpServers": {
"razashariff-proofx": {
"url": "https://proofx-mcp.fly.dev/mcp"
}
}
} {
"servers": {
"razashariff-proofx": {
"type": "http",
"url": "https://proofx-mcp.fly.dev/mcp"
}
}
} [mcp_servers.razashariff-proofx] url = "https://proofx-mcp.fly.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"razashariff-proofx": {
"type": "remote",
"url": "https://proofx-mcp.fly.dev/mcp",
"enabled": true
}
}
} openclaw mcp add razashariff-proofx --url 'https://proofx-mcp.fly.dev/mcp' --transport streamable-http
mcp_servers:
razashariff-proofx:
url: "https://proofx-mcp.fly.dev/mcp" {
"McpServers": {
"razashariff-proofx": {
"Transport": "http",
"Url": "https://proofx-mcp.fly.dev/mcp"
}
}
} assistant mcp add razashariff-proofx -t streamable-http -u 'https://proofx-mcp.fly.dev/mcp'
{
"mcpServers": {
"razashariff-proofx": {
"type": "http",
"url": "https://proofx-mcp.fly.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 17 Sept 26 +7
- Stability: fail → pass ▲ security
- 30 Aug 26 −7
- Stability: pass → fail ▼ security
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Aug 26 0
- Authorization: unverified → fail ▼ critical
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “compute_hash” rewrote its description, which is the text the model reads security
- Tool “get_creator” rewrote its description, which is the text the model reads security
- Tool “my_account” rewrote its description, which is the text the model reads security
- Tool “protect_content” rewrote its description, which is the text the model reads security
- Tool “verify_content” rewrote its description, which is the text the model reads security
- Tool “verify_hash” rewrote its description, which is the text the model reads security
- Tool “protect_content” is now declared destructive security
- Schema quality: 5 → 68 ▼ functional
- “compute_hash” added a required parameter “text”, so existing callers break ▼ functional
- “get_creator” added a required parameter “creator_id”, so existing callers break ▼ functional
- “protect_content” added a required parameter “content_text”, so existing callers break ▼ functional
- “verify_content” added a required parameter “content_id”, so existing callers break ▼ functional
- “verify_hash” added a required parameter “hash”, so existing callers break ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- Schema quality: poor → excellent functional
- Stability: fail → 0.77 functional
- “protect_content” added an optional parameter “creator_id” cosmetic
- “protect_content” added an optional parameter “title” cosmetic
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 20 Sept 2026 · Probed https://proofx-mcp.fly.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.fly.dev | CN=YE1,O=Let's Encrypt,C=US | 21 Aug 2026 | 19 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 688c4daf5300c51e0a5c1f6837a3a67a868 |
| SANs: *.fly.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of proofx-mcp.fly.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| fly.dev. | absent | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://proofx.co.uk https://api.proofx.co.uk; connect-src 'self' https://proofx.co.uk https://api.proofx.co.uk; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://proofx-mcp.fly.dev/mcp | Verified | 200 | |
| http (plaintext) | http://proofx-mcp.fly.dev/mcp | HTTPS enforced | 301 | https://proofx-mcp.fly.dev/mcp |
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 →
compute_hash ~42
Compute the SHA-256 hash of text content locally. Useful for creating a fingerprint of content for verification purposes.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The text content to hash |
No output schema declared.
No examples provided.
get_creator ~58
Look up a ProofX creator's profile, including their identity, certificate details, and content count.
| Name | Type | Req | Description |
|---|---|---|---|
| creator_id | string | yes | The ProofX creator ID (8-character hex string, e.g. 'c1c15c6c') |
No output schema declared.
No examples provided.
my_account ~30
Show the current user's ProofX account information including their creator ID, plan, and content count. Requires authentication.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
protect_content ~143
Register and protect text content with ProofX cryptographic signatures. The content is sent to the ProofX server where the SHA-256 hash is computed and registered for tamper-proof protection. Use this when a user wants to protect their text, article, poem, script, code, or other content they created.
| Name | Type | Req | Description |
|---|---|---|---|
| content_text | string | yes | The text content to protect (article, poem, script, code, lyrics, etc.) |
| creator_id | string | – | ProofX creator ID (8-char hex). If not provided, uses the authenticated session. Get one free at proofx.co.uk |
| title | string | – | A title for the content being protected |
No output schema declared.
No examples provided.
verify_content ~67
Check if digital content is protected with ProofX by its content ID. Returns the creator, protection date, signature status, and content details.
| Name | Type | Req | Description |
|---|---|---|---|
| content_id | string | yes | The ProofX content ID (8-character hex string, e.g. 'a1b2c3d4') |
No output schema declared.
No examples provided.
verify_hash ~68
Verify content authenticity by its SHA-256 hash. Check if a file or text has been registered with ProofX without uploading it. The user should compute the SHA-256 hash of their content first.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | The SHA-256 hash of the file (64-character hex string) |
No output schema declared.
No examples provided.
What is the ProofX - Content Protection for Creators MCP server?
ProofX - Content Protection for Creators is an MCP server listed in the public MCP registry as io.github.razashariff/proofx. Protect and verify digital content with cryptographic signing and proof of ownership. This page covers its hosted endpoint (https://proofx-mcp.fly.dev/mcp).
Is the ProofX - Content Protection for Creators MCP server safe to use?
ProofX - Content Protection for Creators scores 82 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 ProofX - Content Protection for Creators MCP server expose?
ProofX - Content Protection for Creators exposes 6 tools: verify_content, verify_hash, get_creator, protect_content, my_account, compute_hash. Their descriptions and schemas cost roughly 408 tokens of context every time the server is loaded.
Does the ProofX - Content Protection for Creators MCP server require authentication?
No. We connected to ProofX - Content Protection for Creators without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ProofX - Content Protection for Creators MCP server still maintained?
ProofX - Content Protection for Creators is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.