Skip to content

Privi Anchor MCP server

io.github.canoydario847-cloud/privi-anchorcanoydario847-cloudstreamable-httpv0.5.1Scanned

Hash anchoring and proof-of-existence on chain for AI agents and apps. Paid API key required.

8 tools: 6 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 6 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 7
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

6 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 Privi Anchor MCP server can do

The Privi Anchor MCP server is published by the GitHub account canoydario847-cloud. It has 8 tools. It can create or change data (6 tools: anchor_hash_text, anchor_verify, anchor_hashes, anchor_manifest and 2 more), but cannot delete data. 2 tools only read.

7 tools bring in text other people can write (anchor_status, anchor_verify, anchor_hashes and 4 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, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 15, 2026, version 0.5.1.

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.

8 tools

Changes things 6Claude Code: ask
  • anchor_certificateTurn an anchored hash into a readable certificate with a public page: title, owner, fingerprint, block and time.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.

    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
    Turn an anchored hash into a readable certificate with a public page: title, owner, fingerprint, block and time. Useful as dated evidence for designs, drafts, contracts and research notes. The hash must already be anchored and confirmed (anchor_hashes).

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
    • readOnlyHint: false
  • anchor_hash_textSHA-256 of a piece of text, ready to pass to anchor_hashes.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
    SHA-256 of a piece of text, ready to pass to anchor_hashes. Hashing happens here; nothing is stored.

    Annotations the server declares

    • openWorldHint: false
    • readOnlyHint: true
  • anchor_hashesAnchor up to 100 hashes on chain (Base until the Privi chain mainnet) in one transaction.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.

    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
    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).

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
    • readOnlyHint: false
  • anchor_manifestAnchor a whole folder, dataset or evidence bundle with one on-chain transaction.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.

    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
    Anchor a whole folder, dataset or evidence bundle with one on-chain transaction. Later, prove that any one file (by path and fingerprint) was part of it with anchor_manifest_check, without showing the other files. Requires an API key (Authorization: Bearer).

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
    • readOnlyHint: false
  • anchor_manifest_checkCheck that a file (path and fingerprint) was part of an anchored manifest, and that the manifest is on chain.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 that a file (path and fingerprint) was part of an anchored manifest, and that the manifest is on chain. A changed file, or a renamed one, fails.

    Annotations the server declares

    • openWorldHint: true
    • readOnlyHint: true
  • anchor_verifyCheck on the blockchain that a hash was anchored, by whom and when.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 on the blockchain that a hash was anchored, by whom and when. Requires a paid API key. With tx_hash and proof from a receipt, the check uses only chain data.

    Annotations the server declares

    • openWorldHint: true
    • readOnlyHint: true
Only reads 2Show 2 read-only tools
  • anchor_certificate_getRead a proof-of-existence certificate by its ID, with the receipt needed to re-check it on chain.Reads text others writeNo findings

    Why it is in this group

    • The name "anchor_certificate_get" 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
    Read a proof-of-existence certificate by its ID, with the receipt needed to re-check it on chain.

    Annotations the server declares

    • openWorldHint: true
    • readOnlyHint: true
  • anchor_statusWhich chain anchors go to, the service wallet that signs them, its gas balance, and totals.Reads text others writeNo findings

    Why it is in this group

    • The name "anchor_status" says "status": 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
    Which chain anchors go to, the service wallet that signs them, its gas balance, and totals.

    Annotations the server declares

    • openWorldHint: true
    • readOnlyHint: 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 write7
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.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:03 UTC, unchanged since Nov 20, 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
6
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://privi-anchor-zsbk.onrender.com/mcp: tools/list returned 8 tools to an anonymous client, including anchor_hash_text (write), anchor_verify (write), anchor_hashes (write), anchor_manifest (write), anchor_manifest_check (write) and 1 more

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • Tools that change things, listed without credentials: 3 to 6
  2. Oct 29, 2026
    • HTTP status of an anonymous initialize: 404 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 3
    • Protocol version: none to 2025-06-18

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.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 3 -> 6.View diff
    • Tools that change things, listed without credentials: 3 to 6
  2. Tools4 added.+4 addedView diff
  3. Tools1 changed.~1 changedView diff
  4. PostureRemote posture changed. HTTP status of an anonymous initialize: 404 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 3 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 404 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 3
    • Protocol version: none to 2025-06-18

Install

Pinned to version 0.5.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http privi-anchor https://privi-anchor-zsbk.onrender.com/mcp
claude mcp add --transport http privi-anchor https://privi-anchor-zsbk.onrender.com/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__privi-anchor__anchor_status",
      "mcp__privi-anchor__anchor_certificate_get"
    ],
    "ask": [
      "mcp__privi-anchor__anchor_hash_text",
      "mcp__privi-anchor__anchor_verify",
      "mcp__privi-anchor__anchor_hashes",
      "mcp__privi-anchor__anchor_manifest",
      "mcp__privi-anchor__anchor_manifest_check",
      "mcp__privi-anchor__anchor_certificate"
    ],
    "deny": []
  }
}

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 privi-anchor. Review it before you use it.

Capability tags behind 7 rules
  • mcp__privi-anchor__anchor_status untrusted-input
  • mcp__privi-anchor__anchor_verify untrusted-input
  • mcp__privi-anchor__anchor_hashes untrusted-input
  • mcp__privi-anchor__anchor_manifest untrusted-input
  • mcp__privi-anchor__anchor_manifest_check untrusted-input
  • mcp__privi-anchor__anchor_certificate untrusted-input
  • mcp__privi-anchor__anchor_certificate_get 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.canoydario847-cloud/privi-anchor/verify?hash=0b31f94d2f052476f521c14a51ec33b2b20c170c3232fc26db5ed84b5af2b64b" | jq -e '.changed == false'

Pinned hash 0b31f94d2f05, from Nov 15, 2026, 20: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.canoydario847-cloud/privi-anchor/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.canoydario847-cloud/privi-anchor
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.canoydario847-cloud/privi-anchor.svg)](https://radar.anlyon.com/servers/io.github.canoydario847-cloud/privi-anchor)

Source: MCP Registry · repository. Synced Nov 15, 2026, 20:17 UTC.

Privi Anchor MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Privi Anchor MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 6 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 Privi Anchor MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Privi Anchor 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 Privi Anchor MCP server have?

8 tools: 6 write, 2 read. anchor_hash_text, anchor_verify, anchor_hashes, anchor_manifest, anchor_manifest_check, anchor_certificate, anchor_status and anchor_certificate_get.

Does the Privi Anchor MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Privi Anchor MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Privi Anchor MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.