原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚 登录

Proof Of Custody

作者:onrampbtc版本 1.1.0i★ 0i在云端运行官方网站 ↗
注册名称io.github.onrampbtc/proof-of-custody

安装方法

能做什么

Bitcoin custody scores, failure registry, ETF custody, stablecoin and x402 data, source router.

作者提供的原文

  • 连接方式 在云端运行
  • 账号或密钥 无需密钥
  • 分类 加密货币与区块链

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度0/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应8/8上次检查时云端端点有响应
使用分20/100

质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

用一句话让 AI 帮你安装

请帮我安装 Proof Of Custody。按照 https://mcp.popnx.com/i/onrampbtc-proof-of-custody.md 操作,先把命令给我看,等我同意后再运行。

粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文

通过 5/5 项检查 · 你的提问会经过开发者的服务器(proofofcustody.io) · ✓ 命令已检查 2026年11月13日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude · 约 2 分钟

不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加

  1. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. 点击“Add” → “Custom” → “Web”,填写这 2 项

    把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue

    Name · 名称Proof Of Custody
    Remote MCP server URL · 地址https://proofofcustody.io/api/mcp

    在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add

  3. 在聊天中开启

    +ConnectorsProof Of Custody

  4. 试一试

    用 Proof Of Custody 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 Proof Of Custody,或回答中出现 Proof Of Custody 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

能否连接 ChatGPT 取决于方案

完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页

  1. 在网页版 ChatGPT 打开添加 MCP 的页面

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. 填写名称和地址

    输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin

    Name · 名称Proof Of Custody
    Connection · 地址https://proofofcustody.io/api/mcp
  3. 在聊天中选择 Proof Of Custody

    开启新聊天,输入前先从插件列表中选择 Proof Of Custody

  4. 试一试

    用 Proof Of Custody 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 ChatGPT 说正在使用 Proof Of Custody,或回答中出现 Proof Of Custody 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Claude Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  2. 粘贴这条命令并按 Enter

    claude mcp add --transport http --scope user proof-of-custody https://proofofcustody.io/api/mcp
  3. 在 Claude Code 中输入 /mcp

    应能看到 Proof Of Custody 在列表中并显示已连接

  4. 试一试

    用 Proof Of Custody 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 Proof Of Custody,或回答中出现 Proof Of Custody 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  2. 在 Cursor 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 Proof Of Custody 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 Proof Of Custody,或回答中出现 Proof Of Custody 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  2. 在 VS Code 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 Proof Of Custody 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 Proof Of Custody,或回答中出现 Proof Of Custody 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

通过网页连接的应用使用的地址

地址https://proofofcustody.io/api/mcp

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 Proof Of Custody 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

通过网页连接

Claude Code

claude mcp add --transport http --scope user proof-of-custody https://proofofcustody.io/api/mcp

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "proof-of-custody": {
      "url": "https://proofofcustody.io/api/mcp"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "proof-of-custody": {
      "type": "http",
      "url": "https://proofofcustody.io/api/mcp"
    }
  }
}

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

一览

每周下载量i
不在 npm/PyPI 上
许可证i
CC-BY-4.0
连接方式
在云端运行
传输方式
streamable-http
最新版本i
1.1.0
发布到注册中心i
2026年10月20日
代码最后更新i
2026年11月19日
最近检查
2026年11月18日
作者
onrampbtc
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

工具名称和描述与服务器在 2026年11月18日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。

  • search_custody_platforms

    Search Proof of Custody's independent scores for bitcoin and crypto custody platforms. Covers 90+ platforms across exchanges, qualified custodians, ETFs, IRAs, collaborative multisig and multi-institution custody, each scored 0-100 on a published six-category weighted methodology

  • get_custody_platform

    Full Proof of Custody record for one platform: overall score, per-category scores, custody model, fees, insurance position, strengths and limitations. Use after search_custody_platforms, or when a specific provider is named.

  • compare_custody_platforms

    Compare two or more custody platforms side by side on Proof of Custody's scores and custody architecture. Comparison is the shape most useful for a custody decision, because the differences that matter are structural rather than promotional.

  • assess_custody_independence

    Apply the Custody Independence Standard: a published four-pillar test of whether a custody arrangement has genuine independence or only nominal distribution. Pillars are vendor, entropy, control and operational independence. Use for 'how many hardware wallets do I need', 'is my m

  • list_custody_incidents

    The Proof of Custody incident registry: dated records of major bitcoin custody failures from Mt. Gox to the 2026 Coldcard entropy defect, each with root cause, reported loss, the lesson, and which custody configurations the failure class could reach. Self-custody failures are inc

  • get_coldcard_incident_status

    Live status of the July 2026 Coldcard entropy failure: a firmware defect that caused affected hardware wallets to skip their hardware random number generator, making generated keys reconstructible offline. Returns the affected-model matrix with fixed firmware versions, confirmed

  • get_hardware_wallet_scores

    Proof of Custody's hardware wallet rubric: six weighted dimensions — entropy and key generation 25%, firmware integrity 20%, supply chain 15%, disclosure conduct 15%, multisig and recovery portability 15%, privacy and data handling 10%. Entropy is weighted highest because a key g

  • get_etf_custody_concentration

    Filing-derived analysis of custodian concentration across US spot bitcoin ETFs: which custodian holds each fund's bitcoin, and the resulting Nakamoto coefficient at the custody layer. Use for questions about bitcoin ETF safety, IBIT or FBTC custody, whether ETFs are diversified,

  • find_source

    Source router. Given a topic or question about bitcoin or digital-asset market structure (ETF holdings or custodians, stablecoin supply or attestations, tokenized assets, x402 and agent payments, agentic commerce protocols, MCP registries, proof of reserves, regulators and licenc

  • whats_new

    What changed on Proof of Custody since a date: corrections, methodology changes, live incident updates and daily dataset refreshes (stablecoins, tokenized assets, x402, ETF net assets). Use for a scheduled briefing, or to check whether a cached answer went stale. Defaults to the

  • watch_counterparties

    Watchtower for a holder's counterparties. Give it the names of the exchanges, custodians, ETFs, IRA providers or hardware wallets someone uses and it returns, for each, the published custody model and single point of failure, incidents in the registry, hardware rubric status wher

  • search_transcripts

    Full-text search across 320+ Onramp Media podcast transcripts (The Last Trade, Final Settlement and others) for what a guest or host said about a topic. Returns episode, show, date, matching passages and the episode URL. Use for 'what did X say about Y' and for sourcing a quote.

  • route_question

    Routing table lookup. Given a bitcoin custody or market-structure question, returns the matching route: the situation it belongs to, the custody models in play, the Proof of Custody page that answers it, which tool on this server to call next, and the primary sources for the fact

  • fit_custody_setup

    Which bitcoin custody models fit a described situation, by Proof of Custody's published rules, and which platforms run each fitting model by published score. Inputs are banded (amount, who must recover it, what they can do, holder type, jurisdiction, usage, the failure feared mos

  • get_stablecoin_supply

    Daily snapshot of stablecoin supply: total USD-pegged circulating supply, USDT and USDC share, and the top 25 by supply, credited to DefiLlama with the as-of date. Use for 'how big is the stablecoin market', 'USDT vs USDC share', or a stablecoin's supply.

  • get_tokenized_assets

    Daily snapshot of tokenized-asset (RWA) protocols by TVL, credited to DefiLlama, with a pointer to RWA.xyz for issued asset value by class (tokenized Treasuries, credit, commodities). Use for 'how big is tokenization', 'largest RWA protocols', or where to find tokenized Treasury

  • get_x402_services

    Daily snapshot of the x402 agent-payments ecosystem: how many x402-payable services the Coinbase Bazaar lists, by network, asset and scheme, plus the x402 Foundation's 30-day transaction, volume, buyer and seller counts. Use for 'what is x402', 'how many services accept x402', or

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 onrampbtc 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于昨天

  • ✓ 通过

    有许可证

    使用 CC-BY-4.0

  • ✓ 通过

    端点有响应

    在 277 毫秒内响应(HTTP 200)

  • – 不适用

    使用 OAuth 登录

    无需登录

  • ✓ 通过

    工具描述中没有隐藏指令

    已读取 17 个工具描述,未发现针对 AI 的隐藏指令

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/onrampbtc-proof-of-custody.svg)](https://mcp.popnx.com/en/servers/onrampbtc-proof-of-custody)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“加密货币与区块链”中的其他服务器比较i

  • 星标数多于此分类中其他 1779 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 1779 个服务器的 61% 更新
  • 基础检查结果等于或优于此分类中其他 1779 个服务器的 99%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Proof Of Custody 安全吗?

它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于昨天,最新版本(1.1.0)于31天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:DexSQL, PayRam, DexPaprika, Alchemy MCP Server, X402 List MCP

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

DexSQL

SQL for Android APK and DEX files: classes, methods, strings, references and smali.

作者:LSPosed正在增长★ 32333天前更新

在你的电脑上运行✓ lsposed.org

PayRam

Install, configure, operate and integrate self-hosted PayRam crypto payment gateways.

作者:PayRam正在增长★ 15844天前更新

在云端运行✓ 服务方 · payram.com

DexPaprika

DEX and on-chain data: liquidity pools, token prices, swaps, and trading volume.

作者:coinpaprika正在增长★ 1207天前更新

在云端运行✓ 服务方 · dexpaprika.com

X402 List MCP

Find and vet x402 payment APIs before your agent pays one: uptime, price, on-chain volume.

作者:mcccsm起步阶段↓ 80/周★ 1641天前更新

电脑或云端✓ 服务方 · x402-list.com
与相似项目对比
本项
Proof Of Custody
DexSQLPayRamDexPaprikaAlchemy MCP ServerX402 List MCP
运行位置在云端运行,无需安装需要安装在电脑上在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装云端或安装在电脑上都可以
需要密钥否否否否否否
可在 Claude 中按 + 添加否否否否否否
基础检查5/52/33/44/44/45/5
许可证CC-BY-4.0NOASSERTION–MITMITMIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Bitcoin custody dataset

Independent scores, failure history and model definitions for bitcoin custody, published as data rather than as prose. Free to use, including commercially and including to ground or evaluate a model, as long as you say where it came from.

Licence: CC BY 4.0 · Source: proofofcustody.io · Citation: Proof of Custody, Bitcoin custody dataset, https://proofofcustody.io/datasets

Disclosure: Proof of Custody is published by Onramp Bitcoin. Onramp appears in this dataset and is scored by the same methodology as every other platform, including in the categories where it does badly. If you find a place where that is not true, open an issue.


What is in here

FileRowsWhat it holds
data/bitcoin-custody-dataset.json / .csv91 platformsOverall score and all six category scores, custody model, fee display, minimum, audience, and the single point of failure we recorded for each platform
data/custody-incidents.jsonRegistry plus live incidentsDated custody failures, the configurations each failure class could reach, the reported loss and the named source
data/hardware-wallet-scores.jsonAssessed devicesSix-dimension rubric scores with the written rationale for every single score
data/custody-models.json6 modelsWhat each custody model is, who it suits, who it does not suit, and where it fails

Every file is also served live at https://proofofcustody.io/data/ and carries its own citation line, as-of date and disclosure inside the payload.

The scoring methodology

Six weighted categories, applied identically to every platform:

CategoryWeightWhat it measures
Custody and security35%Key management architecture, single points of failure, custodian distribution, physical exposure, jurisdictional diversity, insurance
Ease of use20%Onboarding, interface, operational burden on the holder
Fees15%Total cost of holding, including spreads and custody fees
Features10%Capability that changes what happens to your bitcoin: recovery options, inheritance mechanism, withdrawal controls, trust and entity titling, exit and migration
Transparency10%Proof of reserves, public documentation, disclosure conduct
Support10%Reachability and quality of help when something is wrong

Full methodology, including how to apply it to an arrangement we have never scored: https://proofofcustody.io/methodology

Features was re-scoped on 23 September 2026. It previously rewarded product catalogue breadth (IRA availability, lending, card rewards, DCA, Lightning). Because this site is published by a company that sells several of those products, that definition could award points for resembling the publisher. It now scores only capability that changes custody outcomes. Scores are recomputed under the new definition at the October 2026 run, and the dated entry is in the changelog.

Field reference: platform scores

FieldTypeNotes
name, slug, url, websitestringurl is the Proof of Custody record; website is the platform's own site
categorystringcustody, buy-exchange, ira, etf, yield, hardware
custodyLabelstringThe custody model as operated, for example "Multi-Institution Custody", "Single Custodian", "Collaborative Multisig"
assetClassstring or nullbitcoin, stablecoin, tokenized-asset
overallScoreinteger 0-100Weighted total of the six categories
scoresobjectcustody, ease, fees, features, transparency, support, each 0-100
audienceTypestringWho the platform is built for, in its own terms
minimumInvestment, feeDisplaystringAs published by the platform
singlePointOfFailurestringThe thing that has to fail for the holder to lose access
highlight, riskstringThe strongest and weakest thing we found

Sample queries

# The ten highest custody scores, name and score only

curl -s https://proofofcustody.io/data/bitcoin-custody-dataset.json \ | jq -r '.data | sort_by(-.scores.custody) | .[:10] | .[] | "\(.scores.custody) \(.name)"'

Every platform where one company holds all the keys

curl -s https://proofofcustody.io/data/bitcoin-custody-dataset.json \ | jq -r '.data[] | select(.custodyLabel | test("Single Custodian"; "i")) | .name'

What a given failure class could reach

curl -s https://proofofcustody.io/data/custody-incidents.json \ | jq -r '.incidents[] | "\(.date) \(.name) [\(.exposedConfigs | join(", "))]"'

Hardware rubric, worst entropy scores first, with the reason

curl -s https://proofofcustody.io/data/hardware-wallet-scores.json \ | jq -r '.devices | sort_by(.scores.entropy) | .[] | "\(.scores.entropy) \(.name): \(.rationale.entropy)"'

How to read it honestly

  • Coverage is selected, not exhaustive. A platform that is absent has not been judged unsafe. It has not been scored.
  • Reported is not verified. Loss figures in the registry are as reported by the named source. We have not reproduced on-chain analysis ourselves, and the files say so.
  • Scores carry dates. A platform that shipped a change after its as-of date may have moved. Hardware assessments carry their own asOf.
  • A score is an opinion built from facts. The facts are the citable part. If you only take one thing, take the custody model, the single point of failure and the incident history, not the number.

Updates

Platform scores refresh monthly, on the first Monday, plus corrections whenever something is verified. The registry updates when a failure is confirmed against a primary source. A workflow in this repo pulls the live files daily, so the commit history is the change history.

Corrections and changelog, both public: https://proofofcustody.io/corrections · https://proofofcustody.io/changelog

Agents

There is a read-only MCP server at https://proofofcustody.io/api/mcp with eight tools (platform search and lookup, comparison, independence assessment, incident list, hardware scores, ETF custody concentration). Docs: https://proofofcustody.io/mcp. Same data, same licence, same disclosure inside every tool response.

Corrections

Found something wrong? Open an issue with the primary source. Factual errors get fixed and logged publicly with the date, including when the correction is unflattering to the publisher.