Repository avatar
Other Tools
v1.4.0
active

proveitonchain

io.github.pappyg45/proveitonchain

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

Documentation

proveitonchain-mcp

Give your agent a name on Bitcoin, check other agents' names for free, and token-gate access with TOKENLOCK.

Bitcoin Agent ID: PROVEITBOT

MCP server for Prove It Onchain. Your AI agent can buy its own vanity name on Bitcoin (like SATOSHI), delivered to its own address, and attach an Agent identity: display name, operator, website, X handle, description, agent type/model and MCP endpoint. It can also prove it made, owns, published, or said something first, as a one-of-one token on Bitcoin, paid and signed by the agent's own wallet.

Two products, one server:

  1. Names and proofs on Bitcoin: vanity names with a signed agent profile, one-of-one proofs, free identity and proof checks.
  2. TOKENLOCK, Zero-trust access for the token era: an extra layer in front of your login, admin, or API. Only verified token holders get through. Built for security teams, AI agents, and mining operations. Agents can also sign in to a gated site with a verifiable identity.

This package is a tiny stdio bridge to the hosted server at https://proveitonchain.com/mcp. If your client supports remote (Streamable HTTP) servers, you don't need this package at all: just add that URL.

Non-custodial

The server never holds, sees, or asks for a private key, and it never signs. A name is paid with a normal Bitcoin payment of an exact amount and delivered to the agent's address; editing its Agent identity later needs a message signed by the holder address (BIP-322, or the legacy "sign message" from Unisat, Xverse, Leather, Sparrow, Electrum or Bitcoin Core). create_proof returns an unsigned PSBT that already contains the service fee as one extra output. Your agent signs it with its own wallet, and broadcast checks that it is exactly the transaction that was built (same inputs and outputs, exact fee) before relaying it. You can also broadcast the signed transaction yourself.

When to use it

Use when…ToolsPrice
You are about to trust another agent's claimed identity (it asks you to pay it, or gives you an endpoint or website)verify_agentFree
You or your operator want a persistent, verifiable identity on Bitcoin that other agents and humans can checkcheck_name, buy_name, set_agent_profile$21 + network fee
You need to timestamp an output, file, or claim so it can't be disputed laterget_quote, create_proof, broadcast$1 + network fee
Someone shows you a proof or token and you want to check itverifyFree
You need live proof that someone controls the wallet holding a name right nowcreate_challenge, verify_challengeFree
You want only holders of your Bitcoin token or name to get into your API, site or members areatokenlock_infoTOKENLOCK free plan (100 active wallets a month); paid plans from $19/month in BTC
You need to know whether an address holds a token right nowcheck_token_accessFree
You want to sign in to a TOKENLOCK-gated site with your own Bitcoin name or tokenstart_token_signin, finish_token_signinFree
You're not sure which tool you needproductsFree

No API key, no account.

Install

Claude Desktop (claude_desktop_config.json), or any stdio client:

{
  "mcpServers": {
    "proveitonchain": {
      "command": "npx",
      "args": ["-y", "proveitonchain-mcp"]
    }
  }
}

Remote clients (Cursor, Claude connectors, Claude Code):

{ "mcpServers": { "proveitonchain": { "url": "https://proveitonchain.com/mcp" } } }
claude mcp add --transport http proveitonchain https://proveitonchain.com/mcp

Tools

ToolWhat it does
verify_agentFree. Before trusting another agent's claimed identity: exists on Bitcoin, current owner, whether the profile is signed by that owner, profile fields, registration tx/block/date, verdict. Read-only.
check_nameIs a vanity name available, and its live price ($21 + network fee). Read-only.
buy_nameName + your Bitcoin address (+ optional profile) → order id, exact amount (sats/BTC), pay-to address, expiry.
get_name_orderawaiting_payment → paid → registering → transferring → delivered, with tx ids. Read-only.
cancel_name_orderRelease an unpaid order.
get_agent_profileRead the Agent identity on a name. Read-only.
set_agent_profileAdd or edit the Agent identity, signed by the holder (two calls: get the message, then send the signature).
get_quoteCurrent prices: flat service fee + Bitcoin network fee (min 5 sat/vB). Read-only.
create_proofClaim + optional file / sha256 / metadata + your bc1q address → record, unsigned PSBT (base64 + hex), fee breakdown, signing steps.
broadcastRelay your signed PSBT or raw tx. Checked against the composed tx and exact fee first.
get_proof_statusawaiting_signature / expired / pending / confirmed. Read-only.
verifyAny asset on Bitcoin: facts, proof checks, certificate URL, agent identity. Read-only.
create_challengeFree. Single-use message for the holder of a name to sign (10 minutes).
verify_challengeFree. Checks that signature against the address holding the name right now.
productsFree. Both products and which tools belong to each. Read-only.
tokenlock_infoFree. TOKENLOCK: what it is, plans and prices (monthly active wallets, unlimited sign-ins), install snippets (npm, Express, Cloudflare, PHP), how agents use it, links. Read-only.
check_token_accessFree. Does a Bitcoin address hold a token or name right now (owner or balance)? Read-only, no signature.
start_token_signinFree. Start a "Sign in with your Token" for a TOKENLOCK site (its pk_… site key + origin) or a general pass → message to sign.
finish_token_signinFree. Send your wallet's signature → a short-lived pass the gated site checks.

Live example

PROVEITBOT is a real AI agent with a verified identity on Bitcoin.

  • Agent page: https://proveitonchain.com/agent/PROVEITBOT
  • Its Vanity Name was bought over this MCP server and is held in the agent's own wallet.
  • The agent signed its profile with that wallet, so anyone can check it, and the page shows a green Verified badge.

Try it from any MCP client:

verify_agent { "name": "PROVEITBOT" }

Verify an agent

Use verify_agent (or GET https://proveitonchain.com/api/v1/agents/<NAME>/verify) before trusting another agent's claimed name. It is free and read-only. The verdict is one of:

  • verified: "verified: profile signed by current owner" (the signature is re-checked)
  • profile_unsigned: the name exists and a profile was attached at purchase, but the owner has not signed it
  • no_profile: "name exists, no signed profile"
  • not_registered

Pass the address or profile fields the other agent claimed (for example its mcp_url) and claim_checks shows which match. Rely on the name only when verified and claim_matches are both true.

Badge, green only while the profile is signed by the current owner:

[![Bitcoin Agent ID: PROVEITBOT](https://proveitonchain.com/badge/PROVEITBOT.svg)](https://proveitonchain.com/agent/PROVEITBOT)

Bitcoin Agent ID

Bitcoin Agent ID is a short, open spec for declaring an agent's name on Bitcoin. Put a bitcoin_agent_id object in your A2A agent card (/.well-known/agent.json) and your MCP server metadata:

"bitcoin_agent_id": {
  "spec": "https://proveitonchain.com/agent-id",
  "version": "1",
  "name": "PROVEITBOT",
  "verify_url": "https://proveitonchain.com/api/v1/agents/PROVEITBOT/verify",
  "page_url": "https://proveitonchain.com/agent/PROVEITBOT"
}

Anyone checks it with verify_agent. A verified name proves which Bitcoin address controls the name and signed the profile, and when. It does not prove legal identity, or that an agent or its operator is human or trustworthy. Example: proveitonchain.com/.well-known/agent.json.

TOKENLOCK: zero-trust access for the token era

Zero-trust access for the token era. An extra layer in front of your login, admin, or API. Only verified token holders get through.

TOKENLOCK is a self-serve token gate for security teams, AI agents, and mining operations. Your content stays on your own server. Visitors, people or agents, click Sign in with your Token; Prove It Onchain does the Token check and issues a short-lived pass that your server checks with your secret key. Self-verify (public spec, no dependence on our API) is Coming soon, Enterprise. It is not live yet.

Server-side check recommended. Check the pass on your server so locked content is never sent until we do the Token check. A browser-only setup with gate.js that just hides content in the page is a soft gate: the content still reaches the visitor and can be bypassed with an extension or dev tools. Fine for teasers and soft paywalls, not for anything that must stay private.

For agents, two ways:

  1. Gate your own API, endpoints or members area so only holders of your Bitcoin token or name get in. Create a site in the dashboard (pick the tokens that unlock it; you get a pk_… publishable key and an sk_… secret key), then check every pass server-side:

    import { verifyPass } from '@proveitonchain/tokenlock';
    const v = await verifyPass(pass, { secretKey: process.env.TOKENLOCK_SECRET_KEY });
    if (!v.valid) return res.status(401).end();
    
  2. Sign in to gated sites with a verifiable identity. Buy a Vanity Name with buy_name, sign its profile with set_agent_profile (so others can verify_agent you), then check_token_access → start_token_signin (site key + origin) → sign the message with your own wallet → finish_token_signin → pass. Hand the pass to the site (sites using the npm package or Cloudflare template take it at POST /api/tokenlock/session). Your agent needs to be able to sign a message with the wallet that holds the name; this server never signs for you.

Integrations: npm @proveitonchain/tokenlock (Next.js middleware, Express middleware, React button, any Node server), a Cloudflare Worker template, and a PHP drop-in for shared hosting:

<?php
require_once $_SERVER['DOCUMENT_ROOT'] . '/tokenlock/tokenlock.php';
tokenlock_require();
?>

Plans (paid in BTC): unlimited sign-ins, priced by monthly active wallets (distinct wallets that sign in to your sites in a calendar month; a returning wallet counts once). Free (1 site, 100 active wallets a month) · Starter $19/month (2 sites, 500) · Pro $49/month or $490/year (5 sites, 2,500) · Business $149/month (20 sites, 10,000, webhooks) · Enterprise custom. Extra active wallets about $5 per 1,000; going over never breaks your site.

Docs: https://proveitonchain.com/docs#tokenlock · Live demo: https://proveitonchain.com/vault

Name flow

  1. check_name → available, price.
  2. buy_name with the name, your address and an optional profile → order_id, amount_sats, pay_to, expires_at (30 minutes).
  3. Pay exactly amount_sats to pay_to in one output (the amount includes a 1–999 sat tag that identifies your payment).
  4. Poll get_name_order until delivered. The name is registered on Bitcoin and its ownership transferred to your address. The profile shows at https://proveitonchain.com/agent/<NAME> and on Verify while you hold the name.
  5. Sign the profile with set_agent_profile so verify_agent reports it as verified.

Proof flow

  1. create_proof → unsigned PSBT that issues the token and includes the service fee output.
  2. Sign every input with your wallet (SIGHASH_ALL). Don't change outputs. Finalize.
  3. broadcast with the record_id within 30 minutes.
  4. get_proof_status / verify.

Options

  • PROVEITONCHAIN_MCP_URL (or the first argument) overrides the endpoint.

Fees

Every product is a flat service fee plus the Bitcoin network fee on top (network fee rate is at least 5 sat/vB):

  • Vanity name: $21 + network fee
  • Proof: $1 + network fee
  • Proof of Publication: $1 + network fee
  • Ownership Token: $1 + network fee
  • Certificate of Provenance (art and collectibles): $1 + network fee
  • Verifying an agent or a proof, challenges, token checks and token sign-ins: free
  • TOKENLOCK: free plan, paid plans in BTC (see above)

check_name and get_quote return the live amounts in sats.

What a proof is

A token or Agent identity proves a signed claim, not legal ownership. It shows that the issuer's wallet published a signed, hashed claim at a point in time. It is not legal title, a certificate of authenticity, or proof of legal identity.

Registry

server.json describes the hosted server for the official MCP Registry as io.github.pappyg45/proveitonchain.

License

MIT

Docs: https://proveitonchain.com/docs#mcp · llms.txt: https://proveitonchain.com/llms.txt

No installation packages available.

Remote