ProofX - Content Protection for Creators is an MCP server published by io.github.razashariff, hosted at proofx-mcp.fly.dev. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 6 tools, including verify_content, verify_hash, get_creator, protect_content, my_account.
Protect and verify digital content with cryptographic signing and proof of ownership.
1 connections through 5 shared values. Tap any node.
Inferred from the host name and headers: what a server runs on, not who runs it.
Check if digital content is protected with ProofX by its content ID. Returns the creator, protection date, signature status, and content details.
| Parameter | Type | Description |
|---|---|---|
| content_id * | string | The ProofX content ID (8-character hex string, e.g. 'a1b2c3d4') |
{
"name": "verify_content",
"description": "Check if digital content is protected with ProofX by its content ID. Returns the creator, protection date, signature status, and content details.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"content_id"
],
"properties": {
"content_id": {
"type": "string",
"description": "The ProofX content ID (8-character hex string, e.g. 'a1b2c3d4')"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
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.
| Parameter | Type | Description |
|---|---|---|
| hash * | string | The SHA-256 hash of the file (64-character hex string) |
{
"name": "verify_hash",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"hash"
],
"properties": {
"hash": {
"type": "string",
"maxLength": 64,
"minLength": 64,
"description": "The SHA-256 hash of the file (64-character hex string)"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}Look up a ProofX creator's profile, including their identity, certificate details, and content count.
| Parameter | Type | Description |
|---|---|---|
| creator_id * | string | The ProofX creator ID (8-character hex string, e.g. 'c1c15c6c') |
{
"name": "get_creator",
"description": "Look up a ProofX creator's profile, including their identity, certificate details, and content count.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"creator_id"
],
"properties": {
"creator_id": {
"type": "string",
"description": "The ProofX creator ID (8-character hex string, e.g. 'c1c15c6c')"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| title | string | A title for the content being protected |
| creator_id | string | ProofX creator ID (8-char hex). If not provided, uses the authenticated session. Get one free at proofx.co.uk |
| content_text * | string | The text content to protect (article, poem, script, code, lyrics, etc.) |
{
"name": "protect_content",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"content_text"
],
"properties": {
"title": {
"type": "string",
"default": "Untitled",
"description": "A title for the content being protected"
},
"creator_id": {
"type": "string",
"description": "ProofX creator ID (8-char hex). If not provided, uses the authenticated session. Get one free at proofx.co.uk"
},
"content_text": {
"type": "string",
"description": "The text content to protect (article, poem, script, code, lyrics, etc.)"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": true
}
}Show the current user's ProofX account information including their creator ID, plan, and content count. Requires authentication.
No parameters.
{
"name": "my_account",
"description": "Show the current user's ProofX account information including their creator ID, plan, and content count. Requires authentication.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}Compute the SHA-256 hash of text content locally. Useful for creating a fingerprint of content for verification purposes.
| Parameter | Type | Description |
|---|---|---|
| text * | string | The text content to hash |
{
"name": "compute_hash",
"description": "Compute the SHA-256 hash of text content locally. Useful for creating a fingerprint of content for verification purposes.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"text"
],
"properties": {
"text": {
"type": "string",
"description": "The text content to hash"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Names, descriptions and schemas were written by the server and are shown as data.