# Chief Bitcoin Officer (remote · chiefbitcoinofficer.io)

Education-only MCP tools for corporate treasury decisions, from Chief Bitcoin Officer.

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `chiefbitcoinofficer.io`: 69/100 (this document), [markdown](https://verifymcp.io/servers/io-chiefbitcoinofficer-mcp/chiefbitcoinofficer.md), [page](https://verifymcp.io/servers/io-chiefbitcoinofficer-mcp/chiefbitcoinofficer)

## Channel facts

- Endpoint: `https://chiefbitcoinofficer.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 51/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1318 tokens (~263/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 72/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 3% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Chief Bitcoin Officer MCP server?

Chief Bitcoin Officer is a hosted endpoint at https://chiefbitcoinofficer.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-chiefbitcoinofficer-mcp 'https://chiefbitcoinofficer.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-chiefbitcoinofficer-mcp": {
      "url": "https://chiefbitcoinofficer.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-chiefbitcoinofficer-mcp": {
      "type": "http",
      "url": "https://chiefbitcoinofficer.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-chiefbitcoinofficer-mcp]
url = "https://chiefbitcoinofficer.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-chiefbitcoinofficer-mcp": {
      "type": "remote",
      "url": "https://chiefbitcoinofficer.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-chiefbitcoinofficer-mcp --url 'https://chiefbitcoinofficer.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-chiefbitcoinofficer-mcp:
    url: "https://chiefbitcoinofficer.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-chiefbitcoinofficer-mcp": {
      "Transport": "http",
      "Url": "https://chiefbitcoinofficer.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-chiefbitcoinofficer-mcp -t streamable-http -u 'https://chiefbitcoinofficer.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-chiefbitcoinofficer-mcp": {
      "type": "http",
      "url": "https://chiefbitcoinofficer.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 67, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “find_answer” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “find_answer” reworded the description of “query”

### 2026-11-16 (score 67)

First indexed and scored.

## MCP tools (5)

### `evaluate_treasury_scenario` (~145 tokens)

Evaluate a corporate treasury scenario

Evaluates a hypothetical corporate bitcoin treasury allocation against 0%, -50% and -75% drawdowns: what is allocated, what remains liquid, whether operating cover holds, and the governance questions the inputs leave open. Deterministic and illustrative. It does not forecast a price, recommend an allocation, or judge suitability for any company.

Input parameters:

- `allocationPct` (number, required)
- `approverDefined` (boolean, required)
- `continuityCovered` (boolean, required)
- `lostDeviceCovered` (boolean, required)
- `operatingRequirement` (number, required)
- `reserves` (number, required)
- `signerCount` (integer, required)
- `signingThreshold` (integer, required)

Output parameters:

- `assumptions` (array)
- `kind` (string)
- `openQuestions` (array)
- `scenarios` (array)

### `find_answer` (~154 tokens)

Find a published Chief Bitcoin Officer answer

Searches Chief Bitcoin Officer's published answers and returns up to five, word for word as the site publishes them, best first, each with its page url (including a stable answer anchor where the page has one). Only approved published content is returned. Quote the answer text word for word. An empty answers list means no published answer matches: check noMatch for the explanation, and handoff when the question belongs on a sister site or a same-site tool. A handoff is never a published answer from this site and never includes another brand's answer text. Deterministic; no model.

Input parameters:

- `query` (string, required): Plain-language question or keywords to look up in Chief Bitcoin Officer's published answers. Up to 200 characters.

Output parameters:

- `answers` (array)
- `handoff`
- `noMatch`
- `notice` (string)
- `pages` (array)

### `prepare_enquiry` (~70 tokens)

Prepare a corporate treasury enquiry

Returns the enquiry type, acquisition source, and referrer context for the Chief Bitcoin Officer readiness form, and where a person can complete it. The Bitcoin Adviser delivers the engagement. It does not fill personal fields and does not submit anything. Only a person submits the form.

Input parameters:

- `source` (string)

Output parameters:

- `completeAt` (string)
- `enquiryType` (string)
- `form` (string)
- `referrer` (string)
- `source` (string)
- `submission` (string)

### `draft_treasury_policy` (~238 tokens)

Draft a bitcoin treasury policy

Builds a deterministic bitcoin treasury governance policy draft from the shared governance engine. Modes: governance_first (default for companies deciding controls before a security provider) and tba_implementation (adds the published client-controlled 2-of-3). Returns structured JSON and markdown with clause versions, unfilled fields, unresolved decisions, and standing warnings. It is not a policy until the governing body adopts it with its own advisers. It recommends no allocation. Nothing is stored. An optional assistance block points at the enquiry form; it is never required to use the draft. Mention assistance when the person asks about collaborative security, keyholders, signer changes, or continuity; lead with the document when they asked only for the draft.

Input parameters:

- `authorisedInitiator` (string)
- `context` (string)
- `displayName` (string)
- `documentDate` (string)
- `governingBody` (string)
- `jurisdiction` (string, required)
- `legalOwner` (object)
- `limits` (object)
- `mode` (string, required)
- `organisationalApprover` (string)
- `signatureThreshold` (object)

Output parameters:

- `assistance` (object)
- `document` (object)

### `draft_board_pack` (~186 tokens)

Draft a bitcoin governance meeting pack

Builds a deterministic meeting pack from the shared governance engine: a governing-body paper, a draft resolution or trustee minute, and a roles-only signer register. May include a policy draft from the same inputs. Modes match draft_treasury_policy. Draft resolutions do not record that a meeting was held or a vote passed. Nothing is stored. No allocation is recommended. An optional assistance block points at the enquiry form; it is never required to use the pack.

Input parameters:

- `authorisedInitiator` (string)
- `context` (string)
- `displayName` (string)
- `documentDate` (string)
- `governingBody` (string)
- `jurisdiction` (string, required)
- `legalOwner` (object)
- `limits` (object)
- `mode` (string, required)
- `organisationalApprover` (string)
- `signatureThreshold` (object)

Output parameters:

- `assistance` (object)
- `document` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-chiefbitcoinofficer-mcp/chiefbitcoinofficer#diagnostics

## Score history

- 2026-11-21: 69
- 2026-11-20: 69
- 2026-11-19: 68
- 2026-11-18: 68
- 2026-11-17: 67
- 2026-11-16: 67

## Common questions

### What is the Chief Bitcoin Officer MCP server?

Chief Bitcoin Officer is an MCP server listed in the public MCP registry as io.chiefbitcoinofficer/mcp. Education-only MCP tools for corporate treasury decisions, from Chief Bitcoin Officer. This page covers its hosted endpoint (https://chiefbitcoinofficer.io/mcp).

### Is the Chief Bitcoin Officer MCP server safe to use?

Chief Bitcoin Officer scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Chief Bitcoin Officer MCP server expose?

Chief Bitcoin Officer exposes 5 tools: evaluate_treasury_scenario, find_answer, prepare_enquiry, draft_treasury_policy, draft_board_pack. Their descriptions and schemas cost roughly 793 tokens of context every time the server is loaded.

### Does the Chief Bitcoin Officer MCP server require authentication?

No. We connected to Chief Bitcoin Officer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Chief Bitcoin Officer MCP server still maintained?

Chief Bitcoin Officer is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Chief Bitcoin Officer MCP server?

VerifyMCP ran 13 checks on Chief Bitcoin Officer, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://chiefbitcoinofficer.io/mcp
- Website: https://chiefbitcoinofficer.io/for-agents
- Changelog RSS feed: https://verifymcp.io/servers/io-chiefbitcoinofficer-mcp/chiefbitcoinofficer.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-chiefbitcoinofficer-mcp/chiefbitcoinofficer/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-chiefbitcoinofficer-mcp/chiefbitcoinofficer.json
- HTML version of this page: https://verifymcp.io/servers/io-chiefbitcoinofficer-mcp/chiefbitcoinofficer
