# ProofX - Content Protection for Creators (remote · proofx-mcp.fly.dev)

Protect and verify digital content with cryptographic signing and proof of ownership.

- Trust score: 47/100 (low)
- Change this week: −19
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `proofx-mcp.fly.dev`: 47/100 (this document), [markdown](https://verifymcp.io/servers/razashariff-proofx/proofx-mcp.md), [page](https://verifymcp.io/servers/razashariff-proofx/proofx-mcp)

## Channel facts

- Endpoint: `https://proofx-mcp.fly.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 34/100
  - AI-judged instruction clarity (poor).
  - Tool/resource definitions use about 30 tokens (~5/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 8 days we've observed: 0 tool removals, 5 breaking changes, 0 auth/transport breaks, 0 additions.
- **Tool Coverage**: 0/100
  - 0% of tools have a non-trivial description (not blank, and not just the tool's name).
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add --transport http razashariff-proofx https://proofx-mcp.fly.dev/mcp
```

### Codex

```toml
[mcp_servers.razashariff-proofx]
url = "https://proofx-mcp.fly.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "razashariff-proofx": {
      "type": "remote",
      "url": "https://proofx-mcp.fly.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add razashariff-proofx --url https://proofx-mcp.fly.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  razashariff-proofx:
    url: "https://proofx-mcp.fly.dev/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-07-31 (score 47, −21)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 68, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 65)

First indexed and scored.

## MCP tools (6)

### `verify_content` (~5 tokens)

### `verify_hash` (~5 tokens)

### `get_creator` (~5 tokens)

### `protect_content` (~5 tokens)

### `my_account` (~5 tokens)

### `compute_hash` (~5 tokens)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/razashariff-proofx/proofx-mcp#diagnostics

## Score history

- 2026-08-03: 47
- 2026-08-02: 47
- 2026-08-01: 47
- 2026-07-31: 47
- 2026-07-30: 68
- 2026-07-29: 67
- 2026-07-28: 66
- 2026-07-27: 66
- 2026-07-26: 65

## Links

- Remote endpoint: https://proofx-mcp.fly.dev/mcp
- Repository: https://github.com/razashariff/proofx
- Changelog RSS feed: https://verifymcp.io/servers/razashariff-proofx/proofx-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/razashariff-proofx/proofx-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/razashariff-proofx/proofx-mcp