# Privi Anchor (remote · privi-anchor.onrender.com)

Hash anchoring and proof-of-existence on chain for AI agents and apps. Free with an API key.

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `privi-anchor.onrender.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/canoydario847-cloud-privi-anchor/privi-anchor.md), [page](https://verifymcp.io/servers/canoydario847-cloud-privi-anchor/privi-anchor)

## Channel facts

- Endpoint: `https://privi-anchor.onrender.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.2`

## 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-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 73/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 506 tokens (~126/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 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.
  - Structured output schemas are declared (50% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Privi Anchor MCP server?

Privi Anchor is a hosted endpoint at https://privi-anchor.onrender.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 canoydario847-cloud-privi-anchor 'https://privi-anchor.onrender.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "canoydario847-cloud-privi-anchor": {
      "url": "https://privi-anchor.onrender.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "canoydario847-cloud-privi-anchor": {
      "type": "http",
      "url": "https://privi-anchor.onrender.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.canoydario847-cloud-privi-anchor]
url = "https://privi-anchor.onrender.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "canoydario847-cloud-privi-anchor": {
      "type": "remote",
      "url": "https://privi-anchor.onrender.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add canoydario847-cloud-privi-anchor --url 'https://privi-anchor.onrender.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  canoydario847-cloud-privi-anchor:
    url: "https://privi-anchor.onrender.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "canoydario847-cloud-privi-anchor": {
      "Transport": "http",
      "Url": "https://privi-anchor.onrender.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add canoydario847-cloud-privi-anchor -t streamable-http -u 'https://privi-anchor.onrender.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "canoydario847-cloud-privi-anchor": {
      "type": "http",
      "url": "https://privi-anchor.onrender.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-11-03 (score 75, +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-11-01 (score 74, +1)

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

### 2026-10-30 (score 73, +1)

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

### 2026-10-28 (score 72, +1)

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

### 2026-10-27 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-26 (score 71)

First indexed and scored.

## MCP tools (4)

### `anchor_status` (~28 tokens)

Anchor status

Which chain anchors go to, the service wallet that signs them, its gas balance, and totals.

### `anchor_hash_text` (~50 tokens)

Hash text

SHA-256 of a piece of text, ready to pass to anchor_hashes. Hashing happens here; nothing is stored.

Input parameters:

- `text` (string, required): Exact text to fingerprint (UTF-8)

### `anchor_verify` (~92 tokens)

Verify an anchor

Check on the blockchain that a hash was anchored, by whom and when. Free.
With tx_hash and proof from a receipt, the check uses only chain data.

Input parameters:

- `hash` (string, required): The 64-character hex SHA-256 that was anchored
- `proof`: Optional: Merkle proof from the receipt
- `tx_hash`: Optional: transaction from the receipt, to verify without this server's index

### `anchor_hashes` (~110 tokens)

Anchor hashes

Anchor up to 100 hashes on chain (Base until the Privi chain mainnet) in one transaction. Returns, for each hash, a
receipt (tx_hash, Merkle proof, block, time) that anyone can check with anchor_verify.
Requires an API key (Authorization: Bearer).

Input parameters:

- `hashes` (array, required): 1-100 hex SHA-256 hashes of the content to anchor
- `label` (string): Optional note kept in this server's index (not on chain)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/canoydario847-cloud-privi-anchor/privi-anchor#diagnostics

## Score history

- 2026-11-05: 75
- 2026-11-04: 75
- 2026-11-03: 75
- 2026-11-02: 74
- 2026-11-01: 74
- 2026-10-31: 73
- 2026-10-30: 73
- 2026-10-29: 72
- 2026-10-28: 72
- 2026-10-27: 71
- 2026-10-26: 71

## Common questions

### What is the Privi Anchor MCP server?

Privi Anchor is an MCP server listed in the public MCP registry as io.github.canoydario847-cloud/privi-anchor. Hash anchoring and proof-of-existence on chain for AI agents and apps. Free with an API key. This page covers its hosted endpoint (https://privi-anchor.onrender.com/mcp).

### Is the Privi Anchor MCP server safe to use?

Privi Anchor scores 75 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 Privi Anchor MCP server expose?

Privi Anchor exposes 4 tools: anchor_status, anchor_hash_text, anchor_verify, anchor_hashes. Their descriptions and schemas cost roughly 280 tokens of context every time the server is loaded.

### Does the Privi Anchor MCP server require authentication?

No. We connected to Privi Anchor without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Privi Anchor MCP server still maintained?

Privi Anchor is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Privi Anchor MCP server?

VerifyMCP ran 13 checks on Privi Anchor, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://privi-anchor.onrender.com/mcp
- Repository: https://github.com/canoydario847-cloud/Privi-Network
- Website: https://privi-discovery.onrender.com/
- Changelog RSS feed: https://verifymcp.io/servers/canoydario847-cloud-privi-anchor/privi-anchor.xml
- Changelog JSON feed: https://verifymcp.io/servers/canoydario847-cloud-privi-anchor/privi-anchor/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/canoydario847-cloud-privi-anchor/privi-anchor.json
- HTML version of this page: https://verifymcp.io/servers/canoydario847-cloud-privi-anchor/privi-anchor