Skip to content

Proof Holdings changelog

holdings.proof/mcp-server

22 changes recorded. MCP Harbor re-reads this listing from the official registry every six hours and asks the live server what it exposes, and keeps what changed between one look and the next.

  • Tools +40
    • + pause_proof
    • + resume_proof
    • + get_proof_token
    • + list_reissued_proofs
    • + get_delegation_token
    • + list_my_proofs
    • + get_my_proof
    • + revoke_my_proof
    • + get_company
    • + list_sub_accounts
    • + create_sub_account
    • + get_sub_account
    • + update_sub_account
    • + delete_sub_account
    • + set_primary_sub_account
    • + update_sub_account_page_proofs
    • + get_current_sub_account
    • + update_public_page
    • + list_public_page_proof_options
    • + preview_profile_deletion
    • + preview_email_removal
    • + preview_phone_removal
    • + update_public_page_proofs
    • + resend_confirmation
    • + create_approval_channel
    • + get_approval_channel
    • + list_approval_channels
    • + update_approval_channel
    • + archive_approval_channel
    • + request_approval_channel_authorization
    • + get_approval_channel_keys
    • + upload_approval_channel_keys
    • + delete_approval_channel_keys
    • + get_delegation_carriers
    • + subscribe_lookalike_watch
    • + get_lookalike_watch
    • + cancel_lookalike_watch
    • + list_lookalike_alerts
    • + list_lookalike_reports
    • + proof_holdings_status
  • server.json 1 field changed
    version
    1.8.4 1.10.0

  • server.json 1 field changed
    version
    1.8.3 1.8.4

  • server.json 1 field changed
    version
    1.8.2 1.8.3
  • server.json 1 field changed
    version
    1.8.1 1.8.2
  • server.json 1 field changed
    version
    1.8.0 1.8.1

  • llms.txt +16 −4

    https://proof.holdings/llms.txt

    − 2. **Proof of Delegation** (live) — Authorize a specific MCP server, package or web endpoint from a domain you have proven you control. Each authorization lists what it covers, expires, can be revoked, and comes as a signed token anyone can check offline.− - MCP Server: 167 tools for AI agent integration (Claude, LangChain, CrewAI, any MCP-compatible agent).− - MCP server: `npx -y @proof-holdings/mcp-server` (167 tools)− - Core Primitives: https://proof.holdings/md/docs/primitives.md+ 2. **Proof of Delegation** (live) — Authorize a specific MCP server, package or web endpoint from a domain you have proven you control. Each authorization expires, can be revoked, and comes as a signed token anyone can check offline.+ - MCP Server: 179 tools for AI agent integration (Claude, LangChain, CrewAI, any MCP-compatible agent).+ - MCP server: `npx -y @proof-holdings/mcp-server` (179 tools)+ ## MCP servers verified by Proof Holdings+ An MCP server whose instructions say "Verified by Proof Holdings (delegated by <domain>)" says it runs the Proof Holdings delegation gate with a Proof of Delegation from the owner of <domain>, who proved control of it to Proof Holdings; a gated server refuses its own tool calls once that delegation is revoked, suspended or expired. The line is written once, when the server starts, from the token it was given: it does not change when the delegation is revoked, and any server can write it. It says+ Whether the delegation is in force is what the server's `proof_holdings_status` tool reports. While Proof Holdings is reachable, a revocation reaches a gated server within about 6 minutes at the gate's default interval; while it is not, the server keeps acting on its last answer.+ - `status: valid` — Proof Holdings last answered that the delegation is in force.+ - `status: refused` — the delegation is not in force: Proof Holdings answered so, or the token itself is expired or malformed. The server's other tools refuse too.+ - `reason` says why the delegation was refused: `revoked`, `suspended`, `expired`, `unknown_delegation`, ….+ - `status: unresolved` — the last check could not reach Proof Holdings, and the server is acting on its last answer. `never_validated: true` means it has never had one.+ - `status: not_configured` — the server carries the gate but no delegation token, so nothing is checked.+ - `expires_soon: true` — the delegation expires within 14 days. `source` says whether the answer is `live` or from the server's `cache`.+ The status comes from the server itself and is only as honest as that server. The token is public, so another server can carry the same one: compare the `delegate` the status reports, the artifact the delegation names, with the server you actually installed or connected to. To check one independently:+ - `npx @proof-holdings/proof-check pkg:npm/<name>` finds the published delegation and verifies it locally (exit 0: verified, 1: none found, 2: could not check).+ - The Proof Holdings MCP server's `verify_delegation` tool, or `POST /api/v1/proofs/validate` with the published token.+ - How it works: https://proof.holdings/md/docs/primitives.md

  • server.json 1 field changed
    version
    1.7.2 1.8.0

  • Tools +9
    • + list_webhook_endpoints
    • + get_webhook_endpoint
    • + create_webhook_endpoint
    • + update_webhook_endpoint
    • + delete_webhook_endpoint
    • + rotate_webhook_endpoint_secret
    • + get_balance
    • + list_balance_ledger
    • + rotate_callback_secret
  • server.json 1 field changed
    version
    1.7.1 1.7.2

  • llms.txt +17 −15

    https://proof.holdings/llms.txt

    − > The verification API for humans and AI agents. Seven verification proofs — four live today (Control, Delegation, Action, Me), three coming soon (Agreement, Development, Enforcement) — one API for developers and AI agents.− 1. **Proof of Control** (live) — Verify someone controls a phone, email, or domain. Reverse OTP for phones — the user sends a message TO Proof; email uses magic link or OTP, domains use DNS/HTTP/admin email. Social accounts (OAuth) and crypto wallets (signing) are coming soon.− Positioning: Secure your business with a verification layer.− 2. **Proof of Delegation** (live) — Authorize a specific artifact — an MCP server, a package, an endpoint — from a domain you have proven you control. Every delegation is scoped, expiring and revocable, and mints a signed token anyone can verify offline.− Positioning: Secure your name with signed, revocable delegation.− 3. **Proof of Action** (live) — Human-in-the-loop approvals for irreversible actions. AI agents request sign-off via Telegram or WhatsApp before wires, deploys, or deletions; every decision is cryptographically signed.− Positioning: Secure your irreversible actions with human approval.− 4. **Proof of Agreement** (coming soon — no live API yet) — Continuous witnessing for group conversations: every message in a group you invite Proof into becomes a verifiable record — who said what, when. Starts only when every member agrees.− Positioning: Secure your agreements with an incorruptible witness.− 5. **Proof of Me** (live) — Anti-impersonation reverse verification. Enroll trusted challengers; when someone claiming to be you contacts them, one tap sends you a cross-channel confirmation — you approve or deny.− Positioning: Secure your team with impersonation defense.− 6. **Proof of Development** (coming soon — no live API yet) — Verifiable development provenance: every completed task issues a signed token recording how, what, why, when, by whom, and through what protocol.− Positioning: Secure your codebase with proof of every change.− Positioning: Secure your rules with proof they were followed.− - Billing status: Usage is currently free. Billing isn’t switched on yet, so these prices are what you would pay — nothing is charged today.+ > The verification API for humans and AI agents. Proof Holdings is one API for checking who controls what: that a person controls a phone number, email address or domain; which software a company has authorized under its name; that a real person approved an irreversible action; and that a message claiming to come from you really does.+ 1. **Proof of Control** (live) — Check that someone controls a phone number, email address or domain. For a phone, the person sends a short code from their own Telegram, WhatsApp or SMS to us — the code travels from them, not to them, so there is no incoming code to intercept or phish. Email is checked with a link or a code; a domain with a DNS record, a file on the site, or the admin mailbox. Social accounts and crypto wallets are coming soon.+ Positioning: Know the person really controls the phone, email or domain they gave you.+ 2. **Proof of Delegation** (live) — Authorize a specific MCP server, package or web endpoint from a domain you have proven you control. Each authorization lists what it covers, expires, can be revoked, and comes as a signed token anyone can check offline.+ Positioning: Say publicly which packages and servers you authorized under your name.+ 3. **Proof of Action** (live) — Before an irreversible step — a payment, a deploy, a deletion — your system or AI agent asks a named person to approve it in Telegram or WhatsApp, or any other channel on request. Their yes or no is recorded as a signed proof.+ Positioning: Get a person's signed yes before anything irreversible happens.+ 4. **Proof of Agreement** (coming soon — no live API yet) — Continuous witnessing for group conversations: every message in a group you invite Proof Holdings into becomes a verifiable record — who said what, when. Starts only when every member agrees.+ Positioning: Keep a record of what a group agreed in chat.+ 5. **Proof of Me** (live) — When someone contacts your colleagues or family claiming to be you, they can check with one tap: you get a request on a different channel, you confirm or deny, and they see your answer.+ Positioning: Let the people around you check it's really you.+ 6. **Proof of Development** (coming soon — no live API yet) — Verifiable development provenance: every completed task issues a signed token recording how, what, why, when, by whom, and through which process.+ Positioning: Record how every change to your code was made.+ Positioning: Show that the required steps really ran.+ - Approvals vs an email "yes": https://proof.holdings/md/approvals-vs-email.md+ - Data Processing Agreement: https://proof.holdings/md/dpa.md+ - Subprocessors: https://proof.holdings/md/subprocessors.md

  • server.json 1 field changed
    version
    1.7.0 1.7.1

  • Tools −4
    • − list_profile_templates
    • − update_profile_template
    • − delete_profile_template
    • − preview_profile_template
  • llms.txt +5 −4

    https://proof.holdings/llms.txt

    − 5. **Proof of Me** (live) — Anti-impersonation reverse verification. Enroll trusted challengers; when someone claiming to be you contacts them, one tap sends you a cross-channel confirmation — you approve or deny. Drills keep challengers trained.− - MCP Server: 171 tools for AI agent integration (Claude, LangChain, CrewAI, any MCP-compatible agent).− - Integrations: MCP Server, n8n, Zapier, Make, GitHub Actions.− - MCP server: `npx -y @proof-holdings/mcp-server` (171 tools)+ 5. **Proof of Me** (live) — Anti-impersonation reverse verification. Enroll trusted challengers; when someone claiming to be you contacts them, one tap sends you a cross-channel confirmation — you approve or deny.+ - MCP Server: 167 tools for AI agent integration (Claude, LangChain, CrewAI, any MCP-compatible agent).+ - Integrations: MCP Server, n8n (planned), Zapier (planned), Make (planned), GitHub Actions (planned).+ - MCP server: `npx -y @proof-holdings/mcp-server` (167 tools)+ - Status: https://status.proof.holdings (API, MCP server, public keys for checking proofs, website; JSON data: https://status.proof.holdings/api/getMonitorList/Gy5WBhBMl6; our health check: https://api.proof.holdings/health)

  • server.json 1 field changed
    version
    1.6.0 1.7.0

  • Tools +1 −1
    • + delete_domain_verification
    • − claim_request_assets

  • server.json 1 field changed
    version
    1.5.0 1.6.0

  • server.json 1 field changed
    version
    1.4.0 1.5.0

  • server.json 1 field changed
    version
    1.3.0 1.4.0

  • server.json 1 field changed
    version
    1.1.0 1.3.0
  • llms.txt +2 −2

    https://proof.holdings/llms.txt

    − - MCP Server: 176 tools for AI agent integration (Claude, LangChain, CrewAI, any MCP-compatible agent).− - MCP server: `npx -y @proof-holdings/mcp-server` (176 tools)+ - MCP Server: 171 tools for AI agent integration (Claude, LangChain, CrewAI, any MCP-compatible agent).+ - MCP server: `npx -y @proof-holdings/mcp-server` (171 tools)

  • Tools −5
    • − add_challenger
    • − list_challengers
    • − remove_challenger
    • − invite_challenger
    • − trigger_drill