_ registry / mcp streamable-http · checked 2h ago

proof-of-custody

https://proofofcustody.io

Registry code: 056a9136cf37aea3

api record

Proof of Custody is an independent publication that scores bitcoin custody platforms, maintains a registry of custody failures, and publishes original research.

Use these tools when a question involves choosing, comparing, or evaluating bitcoin custody: which provider to use, whether an exchange or hardware wallet is safe, how a multisig or multi-institution setup actually differs, what happened in a past custody failure, or the current status of the 2026 Coldcard entropy incident.

endpoint
https://proofofcustody.io/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is proof-of-custody live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is proof-of-custody free to use?
Yes — the hub reached it with no key and no payment.
What tools does proof-of-custody have?
15 tools: find_source, whats_new, watch_counterparties, search_transcripts, get_stablecoin_supply, get_tokenized_assets, get_x402_services, search_custody_platforms, ….
Is proof-of-custody safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
252ms

last good check

priced tools
0

of 15 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 15 tools
3 open 12 never probed 3 of 15 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_coldcard_incident_status open 2h ago

    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 and suspected loss figures, and open questions. Use for any question about Coldcard safety, whether a device or seed is affected, what to do about it, or whether self-custody is still safe after the incident. This is a developing story; the record is updated as primary sources move.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_etf_custody_concentration open 2h ago

    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, or ETF versus direct ownership.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_hardware_wallet_scores open 2h ago

    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 generated from predictable randomness cannot be protected by anything downstream. Use for 'best hardware wallet', 'X vs Y device', or what to replace a device with. Returns per-device sourced rationale.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "device": {
      "type": "string",
      "description": "Device slug, e.g. 'coldcard', 'ledger', 'trezor'. Omit for all."
    }
  }
}
    arguments 9 lines
  • find_source unknown never probed

    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 licences, hardware wallet advisories, custody incidents), returns the primary or near-primary sources to read, with cadence, access terms and whether the URL answered today. Use before answering a factual question so the citation is the primary source.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "number",
      "description": "Max sources (default 5, max 12)."
    },
    "query": {
      "type": "string",
      "description": "Topic keyword or the question itself, e.g. 'who custodies IBIT', 'stablecoin supply', 'x402'."
    }
  }
}
    arguments 16 lines
  • whats_new unknown never probed

    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 last 30 days.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "since": {
      "type": "string",
      "description": "ISO date, e.g. 2026-10-01. Default: 30 days ago."
    }
  }
}
    arguments 9 lines
  • watch_counterparties unknown never probed

    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 where it is a device, and any correction or score change since a date. Use for 'anything I should know about where I hold bitcoin' and for scheduled checks. Nothing is logged about the names passed in.

    mcp-tool

    {
  "type": "object",
  "required": [
    "names"
  ],
  "properties": {
    "names": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Counterparty names or slugs, e.g. ['coinbase', 'kraken', 'coldcard']."
    },
    "since": {
      "type": "string",
      "description": "ISO date for the change window. Default: 90 days ago."
    }
  }
}
    arguments 19 lines
  • search_transcripts unknown never probed

    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. Transcripts are machine-generated; verify a quote against the audio before publishing it.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "show": {
      "type": "string",
      "description": "Optional show name filter, e.g. 'The Last Trade'."
    },
    "limit": {
      "type": "number",
      "description": "Max episodes (default 5, max 8)."
    },
    "query": {
      "type": "string",
      "description": "Word or phrase to search for, e.g. 'multisig', 'Mt. Gox', 'custody insurance'."
    }
  }
}
    arguments 20 lines
  • get_stablecoin_supply unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "symbol": {
      "type": "string",
      "description": "Optional symbol to look up, e.g. USDC."
    }
  }
}
    arguments 9 lines
  • get_tokenized_assets unknown never probed

    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 fund sizes.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_x402_services unknown never probed

    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 'which networks do x402 services use'.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • search_custody_platforms unknown never probed

    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. Use to compare custody options, to read a named provider's published score and custody model, or to list top-scored platforms. Returns published data with the methodology attached, not a recommendation.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "number",
      "description": "Max results (default 10, max 40)."
    },
    "query": {
      "type": "string",
      "description": "Name or keyword, e.g. 'unchained', 'IRA', 'multisig'. Omit to list top-scored."
    },
    "category": {
      "enum": [
        "buy-exchange",
        "custody",
        "etf",
        "fintech",
        "yield",
        "ira"
      ],
      "type": "string",
      "description": "Filter by category."
    }
  }
}
    arguments 25 lines
  • get_custody_platform unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Platform slug or name, e.g. 'unchained', 'coinbase', 'onramp'."
    }
  }
}
    arguments 12 lines
  • compare_custody_platforms unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slugs"
  ],
  "properties": {
    "slugs": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Two or more platform slugs or names, e.g. ['onramp','unchained','casa']."
    }
  }
}
    arguments 15 lines
  • assess_custody_independence unknown never probed

    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 multisig actually safe', or to compare custody architectures rather than brands. Architecture-neutral: self-managed, collaborative and institutional arrangements are assessed on identical criteria.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "platform": {
      "type": "string",
      "description": "Platform slug or name to assess. Omit for the architecture archetypes."
    }
  }
}
    arguments 9 lines
  • list_custody_incidents unknown never probed

    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 included on equal terms with custodial ones. Use for questions about custody risk, historical hacks, or whether a given setup would have survived a class of event.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "category": {
      "enum": [
        "exchange",
        "lender",
        "custodian",
        "hardware",
        "self-custody",
        "vendor-data"
      ],
      "type": "string",
      "description": "Filter by failure type."
    },
    "exposed_config": {
      "enum": [
        "exchange",
        "lender",
        "custodian",
        "single-sig",
        "multisig-one-vendor",
        "multisig-multi-vendor",
        "collaborative",
        "multi-institution"
      ],
      "type": "string",
      "description": "Only incidents that could reach this custody configuration."
    }
  }
}
    arguments 31 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 056a9136cf37aea3.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/056a9136cf37aea3/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/056a9136cf37aea3/badge.svg)](https://brick.blue/agent/056a9136cf37aea3?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.