Skip to content

Prove It Onchain MCP server

io.github.pappyg45/proveitonchainpappyg45streamable-httpv1.4.0Scanned

Bitcoin names, proofs and free agent checks, plus TOKENLOCK token-gated access for sites and APIs.

14 tools: 2 can delete or cancel things, 8 change things and 4 only read.

Tools: 2 delete, 0 irreversible, 8 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 14
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here can delete or cancel 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 Prove It Onchain MCP server can do

The Prove It Onchain MCP server is published by the GitHub account pappyg45. It has 14 tools. It can delete or cancel things (2 tools: broadcast and cancel_name_order) and create or change data (8 tools: create_proof, verify, check_name, verify_agent and 4 more). 4 tools only read.

14 tools bring in text other people can write (get_quote, create_proof, broadcast and 11 more); 1 tool can send data out of your system (broadcast).

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 once since Anlyon Radar first saw them.

Last scanned Nov 18, 2026, version 1.4.0.

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.

14 tools

Deletes or cancels 2Claude Code: deny
  • broadcastUse after create_proof, once you have signed the PSBT with your own wallet.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "broadcast" says "broadcast": a word for sending, and what is sent cannot be taken back.
    • The description says "cannot be undone".
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "broadcast" says "broadcast": it sends or publishes something to other people.
    Description, as the server wrote it
    Use after create_proof, once you have signed the PSBT with your own wallet. Relays the signed proof transaction to the Bitcoin network. Send the record_id from create_proof plus either signed_psbt (base64 or hex, finalized or signed) or signed_tx_hex. The server checks it is exactly the transaction it composed and pays the exact service fee, then broadcasts and returns the txid. This spends the coins in the transaction and cannot be undone. Rate limit: 40 per hour per IP. You may also broadcast the signed hex yourself (e.g. mempool.space); the proof is valid either way.

    Annotations the server declares

    • title: Broadcast a signed proof
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • cancel_name_orderUse if you created a name order by mistake or chose a different name.Reads text others writeNo findings

    Why it is in this group

    • The name "cancel_name_order" says "cancel": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).

    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
    Use if you created a name order by mistake or chose a different name. Cancel an unpaid vanity name order and release the name. Refused once a payment has been seen. Do not pay a cancelled order.

    Annotations the server declares

    • title: Cancel an unpaid name order
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
Changes things 8Claude Code: ask
  • buy_nameUse when you or your operator want a persistent, verifiable identity on Bitcoin that other agents and humans can check.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
    Use when you or your operator want a persistent, verifiable identity on Bitcoin that other agents and humans can check. $21 + network fee, paid from any Bitcoin wallet, no API key. Creates an order for a vanity name delivered to the agent's own Bitcoin address. Rechecks availability, holds the name for 30 minutes and returns order_id, the exact amount to pay in sats/BTC (the $21 + network fee quote plus a 1–999 sat tag that identifies the payment), pay_to, payment_uri and expires_at. Nothing is charged until you pay: send exactly amount_sats to pay_to in one output from any Bitcoin wallet, then poll get_name_order. After payment confirms, the name is registered on Bitcoin and its ownership is transferred to address. Optional profile becomes the name's agent profile on delivery; sign it afterwards with set_agent_profile so verify_agent reports it as verified. Rate limit: 8 orders per hour and 3 open orders per IP.

    Annotations the server declares

    • title: Buy a vanity name
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • check_nameUse when you or your operator want a name on Bitcoin and need to know if it is free and what it costs before buying.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
    Use when you or your operator want a name on Bitcoin and need to know if it is free and what it costs before buying. Name $21 + network fee, no API key. Checks whether a vanity name (4–12 letters A–Z, not starting with A; trademarked and brand names are blocked) is available and returns the live price: $21 service fee + network fee, in USD and sats. Read-only; does not reserve the name. Buy it with buy_name.

    Annotations the server declares

    • title: Check a vanity name
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • create_challengeUse when another agent or person claims a name (e.g.Reads text others writeNo findings

    Why it is in this group

    • The name "create_challenge" says "create": a word for a change.

    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
    Use when another agent or person claims a name (e.g. "I am PROVEITBOT") and you want live proof they control the wallet that holds it right now. Free, no API key. Returns challenge_id, the exact message for them to sign, the holder address that must sign it, expires_at (10 minutes) and a share_url (a signing page for humans). Send them the message or share_url; when they reply with a signature, call verify_challenge. Single use. A pass proves wallet control at that moment, not legal identity.

    Annotations the server declares

    • title: Challenge a name holder
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • create_proofUse to timestamp an output, file, or claim so it can't be disputed later: for example a report you generated, a dataset hash, a prediction, or a statement your operator wants on re…Reads text others writeNo findings

    Why it is in this group

    • The name "create_proof" says "create": a word for a change.

    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
    Use to timestamp an output, file, or claim so it can't be disputed later: for example a report you generated, a dataset hash, a prediction, or a statement your operator wants on record. $1 + network fee (publication, deed and artwork $1), no API key. Creates a one-of-one proof token on Bitcoin for a claim, file, or SHA-256, paid and signed by your own wallet. Stores the public claim record and returns an UNSIGNED PSBT (base64 and hex) that issues the token (quantity 1, indivisible, locked) and already includes the service fee output. Nothing is broadcast and no money moves until you sign and call broadcast. Types: proof ($1, needs claim), publication ($1, Proof of Publication: needs metadata.name plus a file, sha256 or metadata.description; the file is hashed and never stored), deed ($1, Ownership Token for a personal item, not legal title: needs metadata.name and a photo as file), artwork ($1, Certificate of Provenance: needs metadata.name, metadata.creator and a photo as file). Files: pass a small file as base64 (or data: URL), an https file_url (up to 6 MB), or just its sha256 so the file never leaves your machine. Then sign every input with the key for address (SIGHASH_ALL), do not change any output, finalize, and call broadcast within 30 minutes. Rate limit: 20 new proofs per hour per IP.

    Annotations the server declares

    • title: Create a proof (unsigned)
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • set_agent_profileUse after your name is delivered to sign its agent profile, so other agents calling verify_agent see "verified: profile signed by current owner".Reads text others writeNo findings

    Why it is in this group

    • The name "set_agent_profile" says "set": a word for a change.

    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
    Use after your name is delivered to sign its agent profile, so other agents calling verify_agent see "verified: profile signed by current owner". Free (no Bitcoin transaction). Adds or edits the agent profile on a name you hold. Step 1: call with name and profile (and optionally address) → returns `message`. Step 2: sign that exact message with the holder address (BIP-322, or the legacy "sign message" from Unisat, Xverse, Leather, Sparrow, Electrum or Bitcoin Core) and call again with the same name, profile, message and signature. The message is valid for 1 hour. Only the current holder can set it.

    Annotations the server declares

    • title: Set an agent identity
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • verifyUse when someone shows you a proof, certificate or token and you want to check it before relying on it, or you need the facts about any asset on Bitcoin.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
    Use when someone shows you a proof, certificate or token and you want to check it before relying on it, or you need the facts about any asset on Bitcoin. Free, no API key. For agent names, verify_agent gives a clearer identity verdict. Looks up any token on Bitcoin by asset name (e.g. A12044707814007245827 or GAMESOFTRUMP). For proofs made on Prove It Onchain it returns the claim, the pass/fail checks (exists, supply is 1, locked, claim record reachable and matching its on-chain hash), owner, creation tx, the certificate URL and the record URL. For other assets it returns their facts (owner, supply, divisibility, lock status) without proof checks. Read-only.

    Annotations the server declares

    • title: Verify an asset
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • verify_agentUse before trusting another agent's claimed identity, for example when an agent says it is PROVEITBOT, asks you to pay it, or gives you an MCP endpoint or website.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
    Use before trusting another agent's claimed identity, for example when an agent says it is PROVEITBOT, asks you to pay it, or gives you an MCP endpoint or website. Free, no API key, read-only. Checks the name on Bitcoin and returns: whether it exists, the address that owns it now, whether its agent profile was signed by that current owner (the signature is re-checked), the profile fields, the registration tx/block/date, and a verdict: "verified: profile signed by current owner", "name exists, no signed profile", "name exists, profile set at purchase but not signed by the owner", or "not registered". Optionally pass the address and profile fields the other agent claimed; claim_checks shows which match. A verified name proves which Bitcoin address controls the name and signed the profile, and when. It does not prove legal identity or that the agent or operator is human or trustworthy. Spec: https://proveitonchain.com/agent-id

    Annotations the server declares

    • title: Verify an agent
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • verify_challengeUse after create_challenge, when the other party returns a signature.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
    Use after create_challenge, when the other party returns a signature. Free. Checks the signature (BIP-322 simple/full or legacy sign-message) against the address that holds the name right now. Returns valid true/false and, on failure, a code: bad_signature, not_holder, holder_changed, expired or already_used. Each challenge can pass once. A pass proves the signer controls the wallet holding the name at that moment, not legal identity.

    Annotations the server declares

    • title: Check a challenge signature
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 4Show 4 read-only tools
  • get_agent_profileUse when you want the raw profile fields of a name.Reads text others writeNo findings

    Why it is in this group

    • The name "get_agent_profile" 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
    Use when you want the raw profile fields of a name. To decide whether to trust an agent, use verify_agent instead. Free. Reads the agent profile attached to a vanity name: display name, operator, website, X handle, description, agent type/model and MCP endpoint, plus the current owner. Shown only while the address that set it still owns the name. Read-only.

    Annotations the server declares

    • title: Get an agent identity
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • get_name_orderUse after buy_name to follow your order until the name is delivered.Reads text others writeNo findings

    Why it is in this group

    • The name "get_name_order" 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
    Use after buy_name to follow your order until the name is delivered. Free. Status of a vanity name order: awaiting_payment, payment_seen, paid, registering, transferring, delivered (or expired, cancelled, needs_review, refunded), with the payment, register and transfer tx ids. Polling also moves a paid order forward. Read-only for the caller.

    Annotations the server declares

    • title: Name order status
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • get_proof_statusUse after broadcast to see whether your proof has confirmed.Reads text others writeNo findings

    Why it is in this group

    • The name "get_proof_status" 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
    Use after broadcast to see whether your proof has confirmed. Free. Status of a proof by record_id: awaiting_signature, expired, pending, or confirmed, with txid, asset, confirmations and links.

    Annotations the server declares

    • title: Proof status
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • get_quoteUse before create_proof to see what a proof will cost right now.Reads text others writeNo findings

    Why it is in this group

    • The name "get_quote" 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
    Use before create_proof to see what a proof will cost right now. Proof $1 + network fee, no API key. Current prices for every proof type. Each is a flat USD service fee plus the Bitcoin network fee on top: proof $1, publication $1, deed (Ownership Token) $1, artwork (Certificate of Provenance) $1. Returns the service fee in USD and sats, the address it is paid to, current network fee rates (sat/vB, never below 5) and an estimated network fee. Read-only; nothing is reserved.

    Annotations the server declares

    • title: Get prices
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: 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.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write14
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
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 18, 2026, 16:20 UTC, unchanged since Nov 18, 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
15
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
  • HighThe whole server

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

    Matched text

    https://proveitonchain.com/mcp: tools/list returned 19 tools to an anonymous client, including broadcast (destructive), cancel_name_order (destructive), create_proof (write), verify (write), check_name (write) and 10 more

    What this check looks for

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. Tools3 added, 11 changed.+3 added~11 changedView diff

Install

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

claude mcp add --transport http proveitonchain https://proveitonchain.com/mcp
claude mcp add --transport http proveitonchain https://proveitonchain.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__proveitonchain__get_quote",
      "mcp__proveitonchain__get_proof_status",
      "mcp__proveitonchain__get_name_order",
      "mcp__proveitonchain__get_agent_profile"
    ],
    "ask": [
      "mcp__proveitonchain__create_proof",
      "mcp__proveitonchain__verify",
      "mcp__proveitonchain__check_name",
      "mcp__proveitonchain__verify_agent",
      "mcp__proveitonchain__buy_name",
      "mcp__proveitonchain__set_agent_profile",
      "mcp__proveitonchain__create_challenge",
      "mcp__proveitonchain__verify_challenge"
    ],
    "deny": [
      "mcp__proveitonchain__broadcast",
      "mcp__proveitonchain__cancel_name_order"
    ]
  }
}

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

Capability tags behind 14 rules
  • mcp__proveitonchain__get_quote untrusted-input
  • mcp__proveitonchain__create_proof untrusted-input
  • mcp__proveitonchain__broadcast untrusted-input, outbound
  • mcp__proveitonchain__get_proof_status untrusted-input
  • mcp__proveitonchain__verify untrusted-input
  • mcp__proveitonchain__check_name untrusted-input
  • mcp__proveitonchain__verify_agent untrusted-input
  • mcp__proveitonchain__buy_name untrusted-input
  • mcp__proveitonchain__get_name_order untrusted-input
  • mcp__proveitonchain__cancel_name_order untrusted-input
  • mcp__proveitonchain__get_agent_profile untrusted-input
  • mcp__proveitonchain__set_agent_profile untrusted-input
  • mcp__proveitonchain__create_challenge untrusted-input
  • mcp__proveitonchain__verify_challenge 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.pappyg45/proveitonchain/verify?hash=ec81f730854281745e686f99885d4444f95d61a08ab8783050b9ab5651a20db6" | jq -e '.changed == false'

Pinned hash ec81f7308542, from Nov 18, 2026, 02: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.pappyg45/proveitonchain/changes.xml

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

Badge

Anlyon Radar badge for io.github.pappyg45/proveitonchain
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.pappyg45/proveitonchain.svg)](https://radar.anlyon.com/servers/io.github.pappyg45/proveitonchain)

Source: MCP Registry · repository. Synced Nov 18, 2026, 03:17 UTC.

Prove It Onchain MCP server: questions and answers

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

Is the Prove It Onchain MCP server safe?

No scan can promise that. What its definitions show: 14 tools, 10 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 Prove It Onchain MCP server delete data?

Yes. 2 tools can delete, cancel or revoke something: broadcast and cancel_name_order.

Can the Prove It Onchain 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 Prove It Onchain MCP server have?

14 tools: 2 destructive, 8 write, 4 read. broadcast, cancel_name_order, create_proof, verify, check_name, verify_agent, buy_name, set_agent_profile and 6 more.

Does the Prove It Onchain MCP server need sign-in or OAuth?

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

Does the Prove It Onchain MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): broadcast.

Has the Prove It Onchain MCP server changed its tools?

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