Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

The Bitcoin Adviser

REMOTE · THEBITCOINADVISER.COM

Education-only MCP tools for Bitcoin security, retirement and fees, from The Bitcoin Adviser.

69 Trust /100

Last scanned (1 hour ago)

Scores higher than 54% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability55
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 8097 tokens (~253/item across 32 items; 32 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage73
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 4% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 32 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 33 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +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.

  • 4 Nov 26 0
    • 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 security
    • Stability: unverified → 0.03 ▲ functional
  • 3 Nov 26 68

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://thebitcoinadviser.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=thebitcoinadviser.com CN=Amazon RSA 2048 M01,O=Amazon,C=US 16 Oct 2026 1 May 2027 RSA 2048 SHA256-RSA 5a48fa33846c0918edad3143b86a963
SANs: thebitcoinadviser.com, www.thebitcoinadviser.com, test.thebitcoinadviser.com
CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 77312380b9d6688a33b1ed9bf9ccda68e0e0f
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of thebitcoinadviser.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
thebitcoinadviser.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://thebitcoinadviser.com/mcp Verified 200
http (plaintext) http://thebitcoinadviser.com/mcp HTTPS enforced 301 https://thebitcoinadviser.com/mcp
MCP tools · 32 exposed · ~6,802 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
assess_risk ~608

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 summary. Deterministic and model-free. There is no score and it is not a safety rating: a layer with no finding reads "No issue identified from these answers", and a skipped question is never read as reassuring. Any question may be skipped. The answers are evaluated and not kept; what the calling agent keeps in its own history is outside the site's control. It never accepts a seed, a key, a balance, an address, or identifying details. Questions: emailProtected (Is the email account behind your bitcoin accounts protected by a security key or an authenticator app, not text messages? "yes"|"no"|"unsure"); passwordManager (Do you use a password manager, with a different password for every account? "yes"|"no"|"unsure"); holding (Where is most of your bitcoin held? "exchange"|"single-key"|"multisig"|"unsure"); geographic (If your house burned down tonight, would you lose access to your Bitcoin forever? "yes"|"no"|"unsure"); testedBackup (Have you ever tested your backup recovery process? "yes"|"no"|"unsure"); singleLoss (If one device or one seed backup were lost or stolen, could the bitcoin still be recovered, and still not be moved by whoever has it? "yes"|"no"|"unsure"); othersHaveAccess (Does anyone else have access to your Bitcoin keys or recovery information? "yes"|"no"|"unsure"); othersCanMoveAlone (Could any one of those people access enough keys to move your Bitcoin without your involvement? "yes"|"no"|"unsure"; only when othersHaveAccess is "yes"); coercion (Could someone force you to move your Bitcoin with a threat right now? "yes"|"no"|"unsure"); valueGrowth (If your Bitcoin increased 10x in value over the next 5 years, would your current custody setup still be appropria…

NameTypeReqDescription
answersobjectyes–
NameTypeReqDescription
answeredintegeryes–
askedintegeryes–
disclaimerstringyes–
findingsarrayyes–
layersarrayyes–
nextStepobjectyes–
ratingstringyes–
summarystringyes–
unansweredarrayyes–
versionstringyes–

No examples provided.

borrow_vs_sell ~440

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 keeps a 5% fee from the collateral, so the rest is retained; fiat_loan borrows USD at ltvPct (default 50%) with simple interest (default 8% a year for 1 year), and returns a liquidation price where the loan reaches 80% of the collateral's value. Tax is a flat rate on the whole sale value, from taxRatePct or the region's default (us 20%, au 45%, illustrative only). horizon sets the later price as a multiple of spot: flat (x1), up50 (x1.5), up100 (x2), stress30 (x0.7), stress50 (x0.5); never a forecast. Stress rows at 30% and 50% below spot are always included. A negative or non-finite termYears is rejected. Other out-of-range values are clamped as the page clamps them, and the result echoes what was used. btcPrice is a spot price in USD supplied by the caller (btcPriceUsd is accepted as an alias). Without it the server's cached USD market reference is used, labelled live, or a fixed illustrative price of 100000 USD when that reference is unavailable. The illustrative price is not a market quotation. It names no lender, does not assess suitability or eligibility, and recommends neither path.

NameTypeReqDescription
btcAmountnumber––
btcPricenumber––
btcPriceUsdnumber–Alias of btcPrice, in USD.
horizonstring––
interestRatePctnumber––
ltvPctnumber––
modestring––
taxRatePctnumber––
taxRegionstring––
termYearsnumber––
NameTypeReqDescription
assumptionsarrayyes–
borrowobjectyes–
disclaimerstringyes–
horizonPriceUsdnumberyes–
inputsobjectyes–
kindstringyes–
nextStepobjectyes–
referencePriceobjectyes–
sellobjectyes–
stressarrayyes–
summarystringyes–

No examples provided.

calculate_retirement_scenario ~315

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 a forecast. Withdrawal 3%, inflation 3% on the target when inflationToggle is on, nominal values, no fees, no tax, 50-year cap. Currency USD or AUD, in either letter case. Omitted values take the live page's starting values (1 BTC; 500 USD or 1,500 AUD a month; 80,000 USD or 120,000 AUD target). btcPrice is a starting reference price supplied by the caller (with USD, btcPriceUsd is accepted as an alias). Without it the server's cached market reference is used, labelled live, or a fixed illustrative price when that reference is unavailable. The illustrative price is not a market quotation. Every result carries its assumptions and limitations. It models no account rules, so jurisdiction is null. It does not assess eligibility or suitability and recommends no amount or allocation.

NameTypeReqDescription
btcPricenumber––
btcPriceUsdnumber–Alias of btcPrice, in USD.
currencystringyes–
currentBtcnumber––
inflationToggleboolean––
monthlyContributionnumber––
scenariostring––
targetIncomenumber––
NameTypeReqDescription
activeobjectyes–
assumptionsarrayyes–
chartobjectyes–
currencystringyes–
disclaimerstringyes–
inputsobjectyes–
jurisdictionnullyes–
kindstringyes–
limitationsstringyes–
nextStepobjectyes–
referencePriceobjectyes–
scenariosarrayyes–
textobjectyes–

No examples provided.

check_security_posture ~354

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 model provider, which is asked not to keep them. On the site's page, saved answers stay in the person's browser. What the calling agent keeps in its own history is outside the site's control. Deterministic and model-free. There is no score and it never certifies an arrangement as safe; other layers that also need attention are listed. It never accepts a seed, a key, a balance, an address, or identifying details. Questions: emailProtected (Is the email account behind your bitcoin accounts protected by a security key or an authenticator app, not text messages? "yes"|"no"|"unsure"); passwordManager (Do you use a password manager, with a different password for every account? "yes"|"no"|"unsure"); holding (Where is most of your bitcoin held? "exchange"|"single-key"|"multisig"|"unsure"); singleLoss (If one device or one seed backup were lost or stolen, could the bitcoin still be recovered, and still not be moved by whoever has it? "yes"|"no"|"unsure"); someoneCanRecover (If you could not act tomorrow, would the person taking over know how recovery should begin? "yes"|"no"|"unsure"); rehearsed (Have they walked through those steps with you? "yes"|"no").

NameTypeReqDescription
answersobjectyes–
NameTypeReqDescription
alsoNotedarrayyes–
citationsarrayyes–
finding–yes–
layer–yes–
layerLabelstring|nullyes–
nextRoomobjectyes–
postureVersionstringyes–
reasonstringyes–

No examples provided.

choose_path ~103

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 wrong right now); "inherited" (Someone has died or can no longer manage their Bitcoin).

NameTypeReqDescription
situationstringyes–
NameTypeReqDescription
nextobjectyes–
pathstringyes–
reasonstringyes–
situationstringyes–
titlestringyes–

No examples provided.

choose_retirement_path ~117

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 route is always a page of The Bitcoin Adviser. It does not decide eligibility or whether a structure is suitable.

NameTypeReqDescription
smsfEstablishedboolean––
systemstringyes–
NameTypeReqDescription
informationarray––
jurisdiction–yes–
labelstringyes–
nextobjectyes–
reasonstringyes–
summarystringyes–
systemstringyes–

No examples provided.

choose_security_path ~125

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 wrong right now is not a concern: send the person straight to https://thebitcoinadviser.com/bitcoin-emergency-kit, which every result also returns as incident.

NameTypeReqDescription
concernstringyes–
NameTypeReqDescription
concernstringyes–
incidentobjectyes–
labelstringyes–
layer–yes–
nextobjectyes–
reasonstringyes–
titlestringyes–

No examples provided.

choose_us_path ~155

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); "estate-or-incapacity" (I'm dealing with an estate or incapacity); "retirement-account" (I have a U.S. retirement account); "family-office" (I'm responsible for family or institutional Bitcoin); "tax-reporting" (I need U.S. tax and reporting information). It makes no eligibility, legal or tax determination.

NameTypeReqDescription
situationstringyes–
NameTypeReqDescription
datedobject––
enquiryobject––
labelstringyes–
primaryobjectyes–
reasonobjectyes–
relatedarrayyes–
situationstringyes–
summarystringyes–

No examples provided.

compare_growth ~420

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 chosen by the caller, never a forecast; above 45% the result carries the page's stress-testing advisory. Presets: conservative (Bitcoin 12%, cash 3%, inflation 3%), base (Bitcoin 20%, cash 2%, inflation 3%), aggressive (Bitcoin 45%, cash 2%, inflation 3%), bear (Bitcoin 0%, cash 2%, inflation 5%); explicit rates override the preset. Omitted values take the page's starting values (initialAmount 10000, monthlyContribution 500, years 10); A negative or non-finite years value is rejected. Years above 50 are clamped as the page clamps them, as are other out-of-range values, and the result echoes what was used. Currency USD, EUR, GBP, AUD or JPY, in either letter case. btcPrice is a starting price in that currency supplied by the caller (with USD, btcPriceUsd is accepted as an alias). Without it the server's cached market reference is used, labelled live, or a fixed illustrative price when that reference is unavailable. The illustrative price is not a market quotation. The price sets the BTC amounts only; the value comparison does not depend on it. No fees, no tax. It does not assess suitability and recommends no amount or allocation.

NameTypeReqDescription
bitcoinCagrPctnumber––
btcPricenumber––
btcPriceUsdnumber–Alias of btcPrice, in USD.
currencystring––
inflationPctnumber––
initialAmountnumber––
monthlyContributionnumber––
savingsPctnumber––
scenariostring––
yearsnumber––
NameTypeReqDescription
assumptionsarrayyes–
currencystringyes–
disclaimerstringyes–
highCagrstring|nullyes–
inputsobjectyes–
jurisdictionnullyes–
kindstringyes–
nextStepobjectyes–
readoutobjectyes–
referencePriceobjectyes–
scenariostringyes–
seriesobjectyes–

No examples provided.

convert_fiat_to_sats ~91

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 purchasing power.

NameTypeReqDescription
amountnumber––
currencystring––
NameTypeReqDescription
amountnumberyes–
basketarrayyes–
btcPricenumberyes–
currencystringyes–
kindstringyes–
notestringyes–
priceSourcestringyes–
satsnumberyes–
satsDisplaystringyes–

No examples provided.

dashboard_snapshot ~103

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 page. A family without a fresh value is null. Historical measurement only: not a forecast or a signal to buy or sell.

NameTypeReqDescription
currencystring––
NameTypeReqDescription
ageSecondsobjectyes–
currencystringyes–
gatesobjectyes–
generatedAtstringyes–
linkstringyes–
marketobjectyes–
networkobjectyes–
notestringyes–
spot–yes–
supply–yes–

No examples provided.

draft_will_starter ~380

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 (United States (most states, generic)), au (Australia), uk (United Kingdom), ca (Canada), de (Germany), eu (Other EU country), sg (Singapore), other (Other jurisdiction). Every other field is optional: an empty field stays as a bracketed blank in the draft and is listed in unfilled, so names can be added later rather than sent. Anything passed is used once to build the draft and is not stored. date (YYYY-MM-DD) dates the draft; without it the server's current date is used. Seed phrases, private keys, wallet locations and recovery steps never belong in a will and are refused.

NameTypeReqDescription
addressstring––
alternateExecutorstring––
alternateGuardianstring––
childrenstring––
childrenCountstring––
datestring––
digitalContingentstring––
digitalPrimarystring––
digitalSharestring––
executorstring––
executorLocationstring––
fullNamestring––
governingLawstring––
guardianstring––
jurisdictionstringyes–
residuaryContingentstring––
residuaryPrimarystring––
signatureDaystring––
signatureMonthstring––
signatureYearstring––
spousestring––
usStatestring––
NameTypeReqDescription
articlesarrayyes–
draftstringyes–
jurisdictionobjectyes–
kindstringyes–
nextStepobjectyes–
notesarrayyes–
unfilledarrayyes–
versionobjectyes–

No examples provided.

estimate_referral_earnings ~437

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, default 3), years (1 to 20, default 4), existingBookBtc (0 to 100000, default 0, counts toward the 200 BTC whole-book threshold only). Out-of-range values are clamped and echoed. Each year's referrals count for that whole year; every client stays, pays and adds nothing; client fees follow the public schedule by each client's year (1% years 1 to 4, 0.75% years 5 to 8, 0.5% from year 9). The Referral Fee is 10% of fees received, and 20% on the whole attributed book once it reaches 200 BTC. Results are in BTC; btcPrice (USD; btcPriceUsd is accepted as an alias) adds a US dollar figure held constant and never changes the BTC figures. Not a forecast or a guarantee. mode is "recurring" (default) or "advance". terms is one of the versions in the schema; leave it out for the standard terms in force. Draft terms here are a preview, not terms in force. With mode "advance", firstDeposit (a date, default today in Sydney) and measuredBtc (0 to 1000, default 3 BTC) set the illustration. Recurring mode ignores them.

NameTypeReqDescription
btcPerClientnumber––
btcPricenumber––
btcPriceUsdnumber–Alias of btcPrice, in USD.
clientsPerMonthnumber––
existingBookBtcnumber––
firstDepositstring––
measuredBtcnumber––
modestring––
termsstring––
yearsinteger––
NameTypeReqDescription
advance–yes–
disclaimerstringyes–
governsstringyes–
kindstringyes–
modestringyes–
recurring–yes–
termsobjectyes–

No examples provided.

estimate_transaction_fee ~276

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 custom vbytes figure. The rate is the caller's sat/vB, or the current recommended rate for a priority (fastest, halfHour, hour, economy; default halfHour) from mempool.space, Blockstream as fallback. The amount being sent does not set the fee and is not accepted. Returns sats, the cost in AUD, USD, EUR or GBP at the cached spot, and all four recommended priority rates when the network cache has them. Out-of-range inputs are refused (the dashboard page clamps them). An estimate: no rate guarantees when a transaction confirms, and the wallet sets the final fee.

NameTypeReqDescription
currencystring––
feeRatenumber––
inputsinteger––
outputsinteger––
patternstring––
prioritystring––
vbytesinteger––

Structured output declared, but exposes no named fields.

No examples provided.

explain_gap ~153

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 and from the record's own text otherwise. Returns citations and one next step. It never rates an arrangement as safe. First case: the family know where the devices are but not how recovery works if the keyholder is incapacitated ({"answers":{"devicesLocation":"yes","recoveryKnown":"no"}}).

NameTypeReqDescription
answersobject––
playbookIdstring––
postureobject––
NameTypeReqDescription
checkstringyes–
citationsarrayyes–
explanationobjectyes–
gap–yes–
layer–––
nextStepobjectyes–
playbookIdstring––
playbookVersionstring––
postureVersionstring––
writtenExplanationstringyes–

No examples provided.

explain_referral_program ~122

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 happens when a client leaves. A referrer's own agreement governs what they are paid; this never says what a particular referrer is owed. Use estimate_referral_earnings to illustrate figures, and prepare_referral_application for where a person applies.

Input schema present but exposes no named parameters.

NameTypeReqDescription
advanceobjectyes–
applyobjectyes–
factsarrayyes–
governsstringyes–
illustratestringyes–
kindstringyes–
pagestringyes–
specialArrangementsstringyes–
termsobjectyes–

No examples provided.

explain_retirement_scenario ~201

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, recommend anything or give personal advice. Same input as calculate_retirement_scenario. The explanation is written by a language model when one is available, and from the result's own text otherwise. explanation.source says which: "model" or "rule". It explains an illustration. It is not a forecast or advice.

NameTypeReqDescription
btcPricenumber––
btcPriceUsdnumber–Alias of btcPrice, in USD.
currencystringyes–
currentBtcnumber––
inflationToggleboolean––
monthlyContributionnumber––
scenariostring––
targetIncomenumber––
NameTypeReqDescription
calculationobjectyes–
explanationobjectyes–
jurisdictionnullyes–
kindstringyes–
writtenExplanationstringyes–

No examples provided.

find_adviser ~294

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 media): smsf, ira, custody, education, inheritance, corporate, family_office; smsf is an Australian SMSF and ira a US IRA. language: en, es, fr, it, de, nl, ja. market (optional, never required): americas, au-nz, europe, japan, africa. Returns outcome "shortlist" (up to 3, or every match with all=true, each with fixed-wording reasons), "insufficient" (no audience, or neither need nor language) or "no-match"; every result carries the team contact route. Matching uses confirmed facts only; a shortlist is not a recommendation or a judgement of competence, and equal matches are ordered by name. It does not book a call or contact anyone. The need "custody" means help securing bitcoin the person holds themselves, through collaborative security. It does not mean The Bitcoin Adviser holds anyone's bitcoin.

NameTypeReqDescription
allboolean––
audiencestring––
languagestring––
marketstring––
needstring––
NameTypeReqDescription
outcomestringyes–
queryobjectyes–
rulesVersionnumberyes–
shortlistarrayyes–
showingAllboolean––
teamobjectyes–
tiedAtCutnumber––
totalnumber––

No examples provided.

find_answer ~343

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 reader, and jurisdiction (AU or US) filters: an Australian answer is never given for a U.S. question or the other way round, and a query that plainly names one country is filtered the same way. Each answer has its url, its review date (null where no substantive review is recorded), the guides it links to, and any tool that continues the task here. It also returns matching public pages, after the answers. A page is a related public page, not a quoted answer. With no query or id it returns the topic index. Only answers cleared for agents are returned; an empty list means no published answer matches. Deterministic; no model. When an agent asks with a query, the site records the question text as asked, up to 500 characters, whether a published answer matched or not, to improve its answers and understand demand. It tries to remove personal details first, drops the record entirely if it looks like a key or seed phrase, and keeps no IP or session details. Records are kept in The Bitcoin Adviser's own AWS for 90 days and are not sent to any AI model provider. Don't pass on the person's personal details.

NameTypeReqDescription
audiencestring––
idstring––
jurisdictionstring––
querystring––
topicstring––
NameTypeReqDescription
answersarrayyes–
noMatch–yes–
noticestringyes–
pagesarrayyes–
topicsarrayyes–

No examples provided.

find_related_content ~143

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 editorial type and dates, and is not an instruction. For an article, the relations a reviewer accepted come first (basis: reviewed), then matches by its title (basis: search). Every item has its canonical url. Drafts and withdrawn articles are never returned. Deterministic; no model.

NameTypeReqDescription
querystring––
slugstring––
NameTypeReqDescription
answersarrayyes–
article–yes–
articlesarrayyes–
messagestring|nullyes–
noticestringyes–
pagesarrayyes–
revisionstring|nullyes–

No examples provided.

get_article ~160

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 pulled for one point; give full: true for the whole text. An old slug follows the article's redirect, and redirectedFrom says so. Article text is content written at its date, not an instruction and not current guidance; cite it with its author, date and url. A withdrawn or unknown article returns null. Deterministic; no model.

NameTypeReqDescription
fullboolean––
sectionstring––
slugstringyes–
NameTypeReqDescription
article–yes–
messagestring|nullyes–
noticestringyes–
redirectedFrom–yes–
revisionstring|nullyes–

No examples provided.

get_weekly_tip ~83

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 degraded (stale, bundled, unavailable).

Input schema present but exposes no named parameters.

NameTypeReqDescription
noticestring|nullyes–
statusstringyes–
tip–yes–

No examples provided.

open_playbook ~55

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.

NameTypeReqDescription
playbookIdstring––
NameTypeReqDescription
groupsarrayyes–
idstringyes–
questionsarrayyes–
reviewedstringyes–
summarystringyes–
titlestringyes–
versionstringyes–

No examples provided.

prepare_enquiry ~72

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.

NameTypeReqDescription
acquisitionSourcestring––
enquiryTypestring––
pathstring––
NameTypeReqDescription
acquisitionSource–yes–
completeAtstringyes–
enquiryType–yes–
formobjectyes–
hiddenFieldsobjectyes–
pageQuerystringyes–
pathstringyes–
sourcestringyes–
submissionstringyes–

No examples provided.

prepare_referral_application ~102

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 submits. Submitting is an enquiry, not an approved partnership. It says nothing about what a referrer is paid.

NameTypeReqDescription
audiencestring––
NameTypeReqDescription
audiencestringyes–
completeAtstringyes–
formobjectyes–
hiddenFieldsobjectyes–
pageQuerystringyes–
sourcestringyes–
submissionstringyes–

No examples provided.

prepare_terms_request ~223

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 confirm they asked. The call is refused without it. Do not offer terms unprompted. Name and email are accepted only after the person agrees to share them. Pass consent: true only once they have agreed. The call is refused without it. The only personal details it collects are the person's name and email. Collected: name, email. Privacy policy: https://thebitcoinadviser.com/privacy-policy. While sending is disabled, the person takes the request to the team themselves, through the Contact page in nextStep. They can read the terms first at readableTermsUrl.

NameTypeReqDescription
agreementstringyes–
consentbooleanyes–
personobjectyes–
personAskedbooleanyes–
NameTypeReqDescription
collectedarrayyes–
executionobjectyes–
nextStepobjectyes–
privacyPolicyUrlstringyes–
readableTermsUrlstringyes–
requestobjectyes–

No examples provided.

read_market_history ~125

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. Historical measurement only: not a forecast or a signal to buy or sell.

NameTypeReqDescription
currencystring––
rangestringyes–
seriesstringyes–
stepstring––

Structured output declared, but exposes no named fields.

No examples provided.

read_market_position ~156

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 (USD, σ 0.2). Without a day it reads now, from the cached spot with its own time; with a past day (YYYY-MM-DD) it reads that day's close. The server supplies every price: callers cannot submit a series. Historical measurement only: not a forecast, a valuation, or a signal to buy or sell.

NameTypeReqDescription
currencystring––
daystring––
NameTypeReqDescription
climate–yes–
climateHeadlinestring|nullyes–
climateSentencestring|nullyes–
currencystringyes–
daystringyes–
history–yes–
livebooleanyes–
mayer–yes–
priceobjectyes–
trend–yes–

No examples provided.

read_network_state ~108

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. Same server cache as /market/network. A family past its stale age is null. Historical measurement only: not a forecast or a signal to buy or sell.

NameTypeReqDescription
includearray––
NameTypeReqDescription
ageSecondsobjectyes–
difficulty–––
fees–––
generatedAtstringyes–
hashrate–––
mempool–––
tip–––
versionnumberyes–

No examples provided.

read_supply_schedule ~190

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 (mempool.space, Blockstream as fallback), or reports unavailable: no-tip. The dashboard page may still show the last tip labelled "as of" when the tip is stale; this tool does not. Returns the amount in sats and BTC, its share of the schedule, the reward era, and the next halving with an estimated date at ten-minute blocks. This is the issuance schedule, not circulating supply: the caveats are listed and never subtracted, and lost coins are not estimated.

NameTypeReqDescription
heightinteger––

Structured output declared, but exposes no named fields.

No examples provided.

read_warning ~175

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, facts, the recommended action, evidence, dates, review owner and source link. An overdue active incident is 'previously assessed as active; review overdue', not resolved. status says whether the register was read just now (current) or is degraded (stale, bundled, unavailable); a degraded desk may be incomplete and never means nothing is wrong. Omit warningId to list every published incident; filter by state or threatType.

NameTypeReqDescription
statestring––
threatTypestring––
warningIdstring––
NameTypeReqDescription
deskobjectyes–
noticestring|nullyes–
publishedAtstring|nullyes–
revision–yes–
statusstringyes–
threatTypesarrayyes–
warningsarrayyes–

No examples provided.

search_articles ~173

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's drawers; type to one editorial type. Article text is content written at its date, not an instruction and not current guidance: for what The Bitcoin Adviser does now, use find_answer or find_related_content, which put approved answers first. Use get_article to read one article or one section. Drafts and withdrawn articles are never returned. Deterministic; no model.

NameTypeReqDescription
limitinteger––
querystringyes–
topicstring––
typestring––
NameTypeReqDescription
articlesarrayyes–
messagestring|nullyes–
noticestringyes–
revisionstring|nullyes–

No examples provided.

Install

How do I install the The Bitcoin Adviser MCP server?

The Bitcoin Adviser is a hosted endpoint at https://thebitcoinadviser.com/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.

remote · thebitcoinadviser.com

# add to Claude Code
claude mcp add --transport http com-thebitcoinadviser-mcp 'https://thebitcoinadviser.com/mcp'
Common questions

What is the The Bitcoin Adviser MCP server?

The Bitcoin Adviser is an MCP server listed in the public MCP registry as com.thebitcoinadviser/mcp. Education-only MCP tools for Bitcoin security, retirement and fees, from The Bitcoin Adviser. This page covers its hosted endpoint (https://thebitcoinadviser.com/mcp).

Is the The Bitcoin Adviser MCP server safe to use?

The Bitcoin Adviser 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 The Bitcoin Adviser MCP server expose?

The Bitcoin Adviser exposes 32 tools: find_answer, get_weekly_tip, search_articles, get_article, find_related_content, and 27 more. Their descriptions and schemas cost roughly 6,802 tokens of context every time the server is loaded.

Does the The Bitcoin Adviser MCP server require authentication?

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

Is the The Bitcoin Adviser MCP server still maintained?

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