Skip to content

Chief Bitcoin Officer MCP server

io.chiefbitcoinofficer/mcpchiefbitcoinofficer.iostreamable-httpv0.1.0Scanned

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

5 tools: 3 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 3 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Chief Bitcoin Officer MCP server can do

The Chief Bitcoin Officer MCP server is published by chiefbitcoinofficer.io, a domain the MCP Registry verified. It has 5 tools. It can create or change data (3 tools: evaluate_treasury_scenario, draft_treasury_policy and draft_board_pack), but cannot delete data. 2 tools only read.

1 tool brings in text other people can write (find_answer).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 16, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 3Claude Code: ask
  • draft_board_packBuilds 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Draft a bitcoin governance meeting pack
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • draft_treasury_policyBuilds a deterministic bitcoin treasury governance policy draft from the shared governance engine.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Draft a bitcoin treasury policy
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • evaluate_treasury_scenarioEvaluates a hypothetical corporate bitcoin treasury allocation against 0%, -50% and -75% drawdowns: what is allocated, what remains liquid, whether operating cover holds, and the g…1 finding

    Why it is in this group

    • The name "evaluate_treasury_scenario" says "evaluate": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "evaluate_treasury_scenario" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "evaluate_treasury_scenario" says "evaluate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Evaluate a corporate treasury scenario
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • find_answerSearches 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.Reads text others writeNo findings

    Why it is in this group

    • The name "find_answer" says "find": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "search" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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. Only approved published content is returned; an empty answers list means no published answer matches. Deterministic; no model.

    Annotations the server declares

    • title: Find a published Chief Bitcoin Officer answer
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • prepare_enquiryReturns the enquiry type, acquisition source, and referrer context for the Chief Bitcoin Officer readiness form, and where a person can complete it.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Prepare a corporate treasury enquiry
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 16, 2026, 14:19 UTC, unchanged since Nov 16, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://chiefbitcoinofficer.io/mcp: tools/list returned 5 tools to an anonymous client, including evaluate_treasury_scenario (write), draft_treasury_policy (write), draft_board_pack (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "evaluate_treasury_scenario" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "evaluate_treasury_scenario" says "evaluate": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__chiefbitcoinofficer__find_answer",
      "mcp__chiefbitcoinofficer__prepare_enquiry"
    ],
    "ask": [
      "mcp__chiefbitcoinofficer__evaluate_treasury_scenario",
      "mcp__chiefbitcoinofficer__draft_treasury_policy",
      "mcp__chiefbitcoinofficer__draft_board_pack"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as chiefbitcoinofficer. Review it before you use it.

Capability tags behind 1 rule
  • mcp__chiefbitcoinofficer__find_answer untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.chiefbitcoinofficer/mcp/verify?hash=861f52fe4d6c582278f607fe219fd2aa6e6f86ae5f1c088e63576271ba6a8758" | jq -e '.changed == false'

Pinned hash 861f52fe4d6c, from Nov 16, 2026, 02:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.chiefbitcoinofficer/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.chiefbitcoinofficer/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.chiefbitcoinofficer/mcp.svg)](https://radar.anlyon.com/servers/io.chiefbitcoinofficer/mcp)

Source: MCP Registry. Synced Nov 16, 2026, 02:17 UTC.

Chief Bitcoin Officer MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Chief Bitcoin Officer MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Chief Bitcoin Officer MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Chief Bitcoin Officer MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Chief Bitcoin Officer MCP server have?

5 tools: 3 write, 2 read. evaluate_treasury_scenario, draft_treasury_policy, draft_board_pack, find_answer and prepare_enquiry.

Does the Chief Bitcoin Officer MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Chief Bitcoin Officer MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Chief Bitcoin Officer MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.