com.thebitcoinadviser/mcp · v0.1.0 · crypto-web3
The Bitcoin Adviser is healthy: it completed an MCP handshake in 3541 ms and exposes 32 tools.
Education-only MCP tools for Bitcoin security, retirement and fees, from The Bitcoin Adviser.
Endpoint: https://thebitcoinadviser.com/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 32 |
| Latency | 3541 ms |
| Last checked (UTC) | 2026-11-03T02:10:34.550Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-11-03T02:10:34.550Z | Healthy | 3541 |
find_answer | Searches The Bitcoin Adviser's published knowledge base and returns up to five answers, word for word as the site publishes them, best first. Ask in the person's own words (query), or open one answer by its id or /faqs anchor (id). topic narrows to one drawer, audience lifts answers written for that |
get_weekly_tip | Returns The Bitcoin Adviser's tip of the week: one published, approved answer selected on Monday (Australia/Sydney) and stored for the whole week. Quote the text word for word and link its url. This is not a live find_answer call. status says whether the tip was read just now (current) or is degrade |
search_articles | Searches the published articles in The Bitcoin Adviser's Journal (articles and guides, from 2023 on) and returns a handful, best first: title, a short excerpt, topics, editorial type, author, original publish date, substantive update date and canonical url. topic narrows to one of the knowledge base |
get_article | Opens one published article from The Bitcoin Adviser's Journal by its slug or url, and returns its author, original publish date, update date, editorial type, canonical url and the anchors of its sections. Give section (an anchor from sections) to read just that section, so a long article is not pul |
find_related_content | For a question (query) or one Journal article (slug or url), returns what The Bitcoin Adviser publishes on the subject: approved answers first, then Journal articles, then the guides, pages and tools they point to. An approved answer is the current guidance; an article is context, labelled with its |
choose_path | Routes a visitor to the right starting point from their situation. Deterministic. Returns the path and the next view. Situations: "protect-for-family" (I hold Bitcoin and want my family to be able to recover it); "adviser" (I advise clients who hold Bitcoin); "something-wrong" (Something has gone wr |
choose_security_path | Routes a Security Centre concern to its one next room. Deterministic. Concerns: "digital-life" (Tighten my digital life, including if I do not hold bitcoin yet); "holding-unsure" (I hold bitcoin and I am not sure it is safe); "family-recovery" (I want my family to be able to recover it). Something w |
choose_retirement_path | Routes by the retirement system the visitor is working with, not by where they live. Deterministic. Systems: "united-states" (United States); "australia" (Australia); "other" (Somewhere else, or no structure yet). For Australia, smsfEstablished=false adds Bitcoin Super as separate information; the r |
choose_us_path | Routes a U.S. visitor by situation to The Bitcoin Adviser's U.S. guidance first: a primary page, related pages, a reason quoted from the primary page, the tax year where the guidance is dated, and an optional enquiry. Deterministic. Situations: "family-future" (I'm planning for my family's future); |
calculate_retirement_scenario | Illustrates how many years Bitcoin holdings plus monthly contributions might take to support a target annual income. Deterministic; the same model as the live retirement explorers. Growth is one of three illustrative scenarios (conservative 12%, base 20%, aggressive 35%), chosen by the caller, never |
explain_retirement_scenario | Runs calculate_retirement_scenario itself and explains the result in plain English. Every number in the explanation comes from the result; text with any other number, or that reads as advice, is replaced by the written explanation. Returns the full calculation too. It does not determine eligibility, |
compare_growth | Illustrates how a lump sum plus monthly contributions might grow in Bitcoin compared with cash savings, nominal and after inflation. Deterministic; the same model as the live Bitcoin Accumulation Calculator. Bitcoin grows on a smooth path at bitcoinCagrPct (0 to 100), an illustrative assumption chos |
convert_fiat_to_sats | Converts an amount of USD, AUD, EUR or GBP into sats at The Bitcoin Adviser's cached spot price (or a fixed fallback when the spot is unavailable), and returns the same conversion for a small basket of everyday items. Illustration only: not a live quote, not financial advice, and not a promise of pu |
borrow_vs_sell | Illustrates the liquidity from selling an amount of Bitcoin after tax, against borrowing on it as collateral, and what each leaves at a later price. Deterministic; the same model as the live Borrowing Against Bitcoin explorer, in USD. mode btc_to_btc borrows BTC at ltvPct (default 95%); the lender k |
read_market_position | The Bitcoin market observatory's reading (/dashboard): the Bitcoin price in AUD, USD, EUR or GBP (default AUD), the Mayer Multiple (price over the mean of the 200 completed UTC daily USD closes, unavailable if any of those days is missing) and the position against the published Power Law model trend |
read_market_history | The dashboard plotter's series (/dashboard): daily Bitcoin price, Mayer Multiple, or Power Law model trend in AUD, USD, EUR or GBP (default AUD), for 1y, 4y or all history, optionally stepped by day, week or month. Points come from the same ledger the page plots, downsampled to at most 500. Historic |
read_supply_schedule | Bitcoin's scheduled cumulative block subsidy through a block height (the dashboard's Supply drawer), from the consensus rule alone: 50 BTC halved every 210,000 blocks, zero from the 64th halving, 2,099,999,997,690,000 sats in all. Without a height it reads the latest block the server has seen (mempo |
estimate_transaction_fee | Estimates a Bitcoin network fee as virtual size × fee rate (the dashboard's fee estimator). The size comes from a named wallet pattern (p2wpkh, p2tr, p2wsh-2of3 or p2sh-p2wsh-2of3, default p2wpkh) with inputs (default 1) and outputs (default 2), using BIP141 weights and stated assumptions, or from a |
read_network_state | The dashboard's network and mempool readings (/dashboard Network and Transactions drawers): tip height, difficulty adjustment, hashrate (series capped at 90 points), recommended fee rates, and mempool count, size and projected or recent blocks (capped at 8 each). Optional include selects families. S |
dashboard_snapshot | One reading of the Bitcoin market dashboard (/dashboard): market position (price, Mayer Multiple, Power Law model trend, climate), spot in all four currencies, network tip, difficulty, hashrate change, four fee rates, mempool summary, and the supply schedule at the tip. Same server caches as the pag |
estimate_referral_earnings | Illustrates potential Referral Fees under The Bitcoin Adviser's standard referral programme terms. Hypothetical inputs only; it never reads or estimates what a real referrer is owed, and a referrer's own agreement governs. Inputs: clientsPerMonth (0 to 100, default 2), btcPerClient (0.1 to 1000, def |
explain_referral_program | Returns the standard terms The Bitcoin Adviser offers new referral partners, as recorded from the agreement: each rule in plain words with its clause, and the terms version they come from. Covers the Referral Fee and the whole-book tier, the client fees it is a share of, when it is paid, and what ha |
find_adviser | Shortlists advisers of The Bitcoin Adviser whose recorded details confirm what was asked. Deterministic, matching rules version 1. audience is holder (a Bitcoin holder or family), professional (an attorney, CPA, notary or family office advising clients) or media (a host or organiser). need (not for |
open_playbook | Returns a versioned Security Centre playbook: checklist groups and items with citations, plus the readiness questions explain_gap accepts. Checklist progress is kept by the caller; this operation stores nothing. |
check_security_posture | Names the one security layer that needs attention (perimeter, holding, control, or continuity) and one next room, from enumerated answers. The answers are sent to the site to work out the result, and are not stored or logged. If the person asks for an explanation, the answers are also sent to an AI |
assess_risk | The full Bitcoin risk assessment: from enumerated answers across the four layers (perimeter, holding, control, continuity), returns every finding in priority order (priority exposure, continuity gap, improvement) with what it means, why it matters and one guide, then each layer's status and a summar |
explain_gap | Reads validated answers, either readiness answers for a playbook (answers) or security posture answers (posture, the same shape check_security_posture takes). Deterministic rules name the gap and, for posture, the layer. The explanation is written from the cited record, by the model when available a |
read_warning | Returns the published warnings register: four evergreen threat types (what multisig limits and what it does not stop), then each published incident with its reviewed state (active or historical), its review freshness (current, or overdue once its review-by date passes), who it applies to, statuses, |
draft_will_starter | Builds the Bitcoin Will Starter's structured draft: a Bitcoin-aware starting point to take to a lawyer where the person lives. It is not a will, not legal advice, and not valid for execution without legal review. Same clause library and wording as the page at /free-bitcoin-will. Jurisdictions: us (U |
prepare_enquiry | Returns the validated path and source context for the client enquiry form, and where a person can complete it. It does not fill personal fields and does not submit anything. Only a person submits the form. |
prepare_referral_application | Returns the client enquiry form for a referral programme enquiry (tba_path=referral) and where a person can complete it, with a validated audience (professional-adviser, community-partner, bitcoiner, or unspecified). It does not fill personal fields and does not submit anything. Only a person submit |
prepare_terms_request | Assembles a request for a person to review: who, which agreement, and an idempotency key. It does not send anything. Sending is a separate, authenticated, human-confirmed step owned by Console, and it is disabled on this site. Use it only when the person asks for terms. Pass personAsked: true to con |