# com.verifyum/mcp (remote · api.verifyum.com)

Privacy-preserving file proofs on Solana. Files are hashed locally. Currently free, no API key.

- Trust score: 82/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `api.verifyum.com`: 82/100 (this document), [markdown](https://verifymcp.io/servers/com-verifyum-mcp/api.md), [page](https://verifymcp.io/servers/com-verifyum-mcp/api)

## Channel facts

- Endpoint: `https://api.verifyum.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-09-20.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: signatures are present but failed validation.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 502 tokens (~167/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the com.verifyum/mcp server?

com.verifyum/mcp is a hosted endpoint at https://api.verifyum.com/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.

### Claude

```bash
claude mcp add --transport http com-verifyum-mcp 'https://api.verifyum.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-verifyum-mcp": {
      "url": "https://api.verifyum.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-verifyum-mcp": {
      "type": "http",
      "url": "https://api.verifyum.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-verifyum-mcp]
url = "https://api.verifyum.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-verifyum-mcp": {
      "type": "remote",
      "url": "https://api.verifyum.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-verifyum-mcp --url 'https://api.verifyum.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-verifyum-mcp:
    url: "https://api.verifyum.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-verifyum-mcp": {
      "Transport": "http",
      "Url": "https://api.verifyum.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-verifyum-mcp -t streamable-http -u 'https://api.verifyum.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-verifyum-mcp": {
      "type": "http",
      "url": "https://api.verifyum.com/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-09-20 (score 82, +1)

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

### 2026-09-18 (score 81, +1)

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

### 2026-09-16 (score 80, +1)

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

### 2026-09-14 (score 79, +1)

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

### 2026-09-12 (score 78, +1)

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

### 2026-09-10 (score 77, +1)

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

### 2026-09-08 (score 76, +1)

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

### 2026-09-05 (score 75, +1)

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

## MCP tools (3)

### `verifyum_get_proof` (~54 tokens)

Get Verifyum proof status

Read the lifecycle state of one Verifyum proof (queued, submitted, finalized or failed). Input is a public proof ID only.

Input parameters:

- `proof_id` (string, required): A canonical 26-character Verifyum proof ID

### `verifyum_verify_public_proof` (~146 tokens)

Verify a public Verifyum proof

Check a finalized proof: metadata consistency, the exact 128-byte memo, and the Ed25519 service signature against the published key registry. The response also contains the exact Solana RPC call and expectations so the caller can independently confirm the transaction on chain, because this hosted check is performed by the Verifyum service itself. A finalized Verifyum anchor demonstrates that a commitment to exact file bytes existed no later than the estimated Solana block time. It does not prove authorship, ownership, legal signature validity, when the file was first created, or whether statements inside the file are true.

Input parameters:

- `proof_id` (string, required): A canonical 26-character Verifyum proof ID

### `verifyum_anchor_commitment` (~200 tokens)

Anchor a prepared Verifyum commitment

Submit one locally calculated Verifyum version 2 commitment. Accepts only the commitment and an idempotency key. Never send a file, filename, raw file hash, nonce or private manifest. The caller must hash the file and build the private manifest on its own machine first, as documented at https://verifyum.com/agents. This creates a real public transaction on Solana Mainnet. Public use is currently free and the network fee is currently paid by AI SENSE AS. That is a current service policy, not a permanent pricing guarantee. Create proofs only on clear user intent, never speculatively, in bulk, or as a hidden side effect. When retrying, reuse the exact same commitment and idempotency key.

Input parameters:

- `commitment` (string, required): sha256: followed by 64 lowercase hexadecimal characters
- `idempotency_key` (string, required): 16 to 128 URL-safe characters, reused verbatim on retries

## Diagnostics

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

## Score history

- 2026-09-20: 82
- 2026-09-19: 81
- 2026-09-18: 81
- 2026-09-17: 80
- 2026-09-16: 80
- 2026-09-15: 79
- 2026-09-14: 79
- 2026-09-13: 78
- 2026-09-12: 78
- 2026-09-11: 77
- 2026-09-10: 77
- 2026-09-09: 76
- 2026-09-08: 76
- 2026-09-07: 75
- 2026-09-06: 75
- 2026-09-05: 75
- 2026-09-04: 74
- 2026-09-03: 74
- 2026-09-02: 73
- 2026-09-01: 73
- 2026-08-31: 72

## Common questions

### What is the com.verifyum/mcp server?

com.verifyum/mcp is listed in the public MCP registry as com.verifyum/mcp. Privacy-preserving file proofs on Solana. Files are hashed locally. Currently free, no API key. This page covers its hosted endpoint (https://api.verifyum.com/mcp).

### Is the com.verifyum/mcp server safe to use?

com.verifyum/mcp 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 com.verifyum/mcp server expose?

com.verifyum/mcp exposes 3 tools: verifyum_get_proof, verifyum_verify_public_proof, verifyum_anchor_commitment. Their descriptions and schemas cost roughly 400 tokens of context every time the server is loaded.

### Does the com.verifyum/mcp server require authentication?

No. We connected to com.verifyum/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the com.verifyum/mcp server still maintained?

com.verifyum/mcp 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.

## Links

- Remote endpoint: https://api.verifyum.com/mcp
- Website: https://verifyum.com/agents
- Changelog RSS feed: https://verifymcp.io/servers/com-verifyum-mcp/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-verifyum-mcp/api.json
- HTML version of this page: https://verifymcp.io/servers/com-verifyum-mcp/api