ProofX - Content Protection for Creators MCP server
io.github.razashariff/proofxrazashariffstreamable-httpv1.0.0Scanned
Protect and verify digital content with cryptographic signing and proof of ownership.
6 tools: 1 can delete or cancel things, 3 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 5
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the ProofX - Content Protection for Creators MCP server can do
The ProofX - Content Protection for Creators MCP server is published by the GitHub account razashariff. It has 6 tools. It can delete or cancel things (1 tool: protect_content) and create or change data (3 tools: verify_content, verify_hash and compute_hash). 2 tools only read.
5 tools bring in text other people can write (verify_content, verify_hash, get_creator and 2 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 20, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Deletes or cancels 1Claude Code: deny
protect_contentRegister and protect text content with ProofX cryptographic signatures.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
Changes things 3Claude Code: ask
compute_hashCompute the SHA-256 hash of text content locally.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Compute the SHA-256 hash of text content locally. Useful for creating a fingerprint of content for verification purposes.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
verify_contentCheck if digital content is protected with ProofX by its content ID.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Check if digital content is protected with ProofX by its content ID. Returns the creator, protection date, signature status, and content details.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
verify_hashVerify content authenticity by its SHA-256 hash.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 2Show 2 read-only tools
get_creatorLook up a ProofX creator's profile, including their identity, certificate details, and content count.Reads text others writeNo findings
Why it is in this group
- The name "get_creator" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Look up a ProofX creator's profile, including their identity, certificate details, and content count.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
my_accountShow the current user's ProofX account information including their creator ID, plan, and content count.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "show": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Show the current user's ProofX account information including their creator ID, plan, and content count. Requires authentication.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write5
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:10 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://proofx-mcp.fly.dev/.well-known/oauth-protected-resource
- Authorization servers
- https://proofx-mcp.fly.dev
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (1 destructive, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://proofx-mcp.fly.dev/mcp: tools/list returned 6 tools to an anonymous client, including protect_content (destructive), verify_content (write), verify_hash (write), compute_hash (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http proofx https://proofx-mcp.fly.dev/mcpclaude mcp add --transport http proofx https://proofx-mcp.fly.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__proofx__get_creator",
"mcp__proofx__my_account"
],
"ask": [
"mcp__proofx__verify_content",
"mcp__proofx__verify_hash",
"mcp__proofx__compute_hash"
],
"deny": [
"mcp__proofx__protect_content"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as proofx. Review it before you use it.
Capability tags behind 5 rules
- mcp__proofx__verify_content untrusted-input
- mcp__proofx__verify_hash untrusted-input
- mcp__proofx__get_creator untrusted-input
- mcp__proofx__protect_content untrusted-input
- mcp__proofx__my_account untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.razashariff/proofx/verify?hash=851da0bbeb148eb37f8cc0cb5a13c69986c3290a4141658b6d8b768258ca1434" | jq -e '.changed == false'Pinned hash 851da0bbeb14, from Nov 20, 2026, 09:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.razashariff/proofx/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.razashariff/proofx)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:45 UTC.
ProofX - Content Protection for Creators MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the ProofX - Content Protection for Creators MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the ProofX - Content Protection for Creators MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: protect_content.
Can the ProofX - Content Protection for Creators MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the ProofX - Content Protection for Creators MCP server have?
- 6 tools: 1 destructive, 3 write, 2 read. protect_content, verify_content, verify_hash, compute_hash, get_creator and my_account.
Does the ProofX - Content Protection for Creators MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the ProofX - Content Protection for Creators MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the ProofX - Content Protection for Creators MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.