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.

Bitcoin Super

REMOTE · BITCOINSUPER.IO

Education-only MCP tools for Bitcoin in Australian SMSFs, from Bitcoin Super.

Available components

71 Trust /100

Last scanned (17 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

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
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 965 tokens (~193/item across 5 items; 5 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 Management17
  • Stability observed for 5 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
  • 6% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +1

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

  • 19 Nov 26 +1

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

  • 17 Nov 26 +1
    • 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
    • Schema quality: 170 → 193 ▼ functional
    • Tool coverage: 0% → 6% ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • “find_answer” reworded the description of “query” cosmetic
  • 16 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 21 Nov 2026 · Probed https://bitcoinsuper.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=bitcoinsuper.io CN=Amazon RSA 2048 S19,O=Amazon,C=US 12 Nov 2026 30 May 2027 RSA 2048 SHA256-RSA 404ffb75e10c5d7f1c2f933aeb071d8c
SANs: bitcoinsuper.io, www.bitcoinsuper.io
CN=Amazon RSA 2048 S19,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 8 Jul 2026 7 Jul 2029 RSA 2048 SHA256-RSA 3e66530c008bab6b9a6d90c1f0d323dac30eeeca
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 bitcoinsuper.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
bitcoinsuper.io. No DS 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://bitcoinsuper.io/mcp Verified 200
http (plaintext) http://bitcoinsuper.io/mcp HTTPS enforced 301 https://bitcoinsuper.io/mcp
MCP tools · 5 exposed · ~550 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
calculate_smsf_scenario ~201

Runs the Bitcoin Super SMSF scenario model: Managed Superfund versus Bitcoin Super tracks with contributions, Transfer Balance Cap split, and minimum pension drawdowns. Optional Advanced fields cover inflation and spending coverage (web v2.2). Outputs are illustrations under published assumptions on /assumptions, not forecasts, advice, or suitability scores. Constants claim 2026-27 ATO figures and must be treated as dated. Seed phrases and private keys are refused.

NameTypeReqDescription
annualContributionnumber––
btcCagrnumber––
currentAgeinteger––
fundCagrnumber––
inflationPctnumber––
initialnumberyes–
otherIncomeTodaynumber––
planningEndAgeinteger––
presetstring––
retirementAgeinteger––
spendingTodaynumber––
useAgesboolean––
NameTypeReqDescription
btcCoveragePctnumber|nullyes–
btcFinalnumberyes–
constantsReviewedAtstringyes–
effectiveAnnualnumberyes–
fundCoveragePctnumber|nullyes–
fundFinalnumberyes–
gapnumberyes–
methodologystringyes–
noticestringyes–
totalContributionsnumberyes–
transferBalanceCapnumberyes–
yearsnumberyes–

No examples provided.

find_answer ~152

Searches Bitcoin Super'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.

NameTypeReqDescription
querystringyesPlain-language question or keywords to look up in Bitcoin Super's published answers. Up to 200 characters.
NameTypeReqDescription
answersarrayyes–
handoff–yes–
noMatch–yes–
noticestringyes–
pagesarrayyes–

No examples provided.

handoff_tba ~62

Returns The Bitcoin Adviser URLs for services Bitcoin Super does not implement: SMSF audit guide, EOFY checklist, Collaborative Security, historical valuation, and estate continuity. Bitcoin Super remains the educational publisher; TBA delivers those services.

NameTypeReqDescription
topicstringyes–
NameTypeReqDescription
notestringyes–
ownerstringyes–
topicstringyes–
urlstringyes–

No examples provided.

prepare_enquiry ~94

Returns the gold-form context for a free Bitcoin SMSF consultation on Bitcoin Super: referrer bitcoinsuper.io (HubSpot enum), acquisition source, and where a person completes the form. It does not fill personal fields and does not submit anything. Only a person submits. The lead is directed to Andy; the website does not assign a TBA adviser.

NameTypeReqDescription
pathstring––
sourcestring––
NameTypeReqDescription
completeAtstringyes–
conversionPathstringyes–
enquiryTypestringyes–
formstringyes–
referrerstringyes–
sourcestringyes–
submissionstringyes–

No examples provided.

read_assumptions ~41

Returns the published Bitcoin Super calculator constants, presets, exclusions summary, and methodology label. Figures are dated site claims pending ATO revalidation. Not advice.

Input schema present but exposes no named parameters.

NameTypeReqDescription
constantsobjectyes–
exclusionsarrayyes–
methodologystringyes–
presetsobjectyes–
sharedCorestringyes–
urlstringyes–
webOnlyAdvancedarrayyes–

No examples provided.

Install

How do I install the Bitcoin Super MCP server?

Bitcoin Super is a hosted endpoint at https://bitcoinsuper.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.

remote · bitcoinsuper.io

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

What is the Bitcoin Super MCP server?

Bitcoin Super is an MCP server listed in the public MCP registry as io.bitcoinsuper/mcp. Education-only MCP tools for Bitcoin in Australian SMSFs, from Bitcoin Super. This page covers its hosted endpoint (https://bitcoinsuper.io/mcp).

Is the Bitcoin Super MCP server safe to use?

Bitcoin Super scores 71 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 Bitcoin Super MCP server expose?

Bitcoin Super exposes 5 tools: find_answer, calculate_smsf_scenario, prepare_enquiry, read_assumptions, handoff_tba. Their descriptions and schemas cost roughly 550 tokens of context every time the server is loaded.

Does the Bitcoin Super MCP server require authentication?

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

Is the Bitcoin Super MCP server still maintained?

Bitcoin Super 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 Bitcoin Super MCP server?

VerifyMCP ran 13 checks on Bitcoin Super, 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.