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.

Bankrolled.ai Agent Hub

REMOTE · BANKROLLED.AI

Free, sourced deposit-insurance/savings/retirement limits. US, UK, CA, AU, NZ. No key, no payment.

Available components

0 this week 82 Trust /100

Last scanned (12 hours ago)

Scores higher than 81% 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 Security63
  • 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 check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability81
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 902 tokens (~180/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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.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 supported MCP spec version (2025-11-25); the latest is 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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 +1
    • Stability: 0.97 → pass security
  • 4 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 3 Nov 26 0
    • Server version: 1.5.8 → 1.5.9 functional
  • 2 Nov 26 0
    • Server version: 1.5.7 → 1.5.8 functional
  • 28 Oct 26 0
    • Server version: 1.5.6 → 1.5.7 functional
    • Tool “cross_border_check” changed its title: Cross-Border Deposit Protection Check cosmetic
    • Tool “health_check” changed its title: Server Health Check cosmetic
    • Tool “money_fact” changed its title: Official Money Limit Lookup cosmetic
    • Tool “pricing_list” changed its title: List Covered Facts and Countries cosmetic
    • Tool “scheme_lookup” changed its title: Deposit Insurance Scheme Lookup cosmetic
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://bankrolled.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=bankrolled.ai CN=WE1,O=Google Trust Services,C=US 30 Oct 2026 28 Jan 2027 ECDSA 256 ECDSA-SHA256 8705571d3b8391d61350c75808fc4966
SANs: bankrolled.ai, *.bankrolled.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of bankrolled.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
bankrolled.ai. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://bankrolled.ai/mcp Verified 200
http (plaintext) http://bankrolled.ai/mcp Served over HTTP 200
MCP tools · 5 exposed · ~578 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
cross_border_check ~168

Answer cross-border money questions: deposit protection for non-residents, which schemes cover accounts held across borders. Returns sourced scheme information for both countries (from_country and to_country) with official regulator URLs and as_of dates. Covers US, UK, CA, AU, NZ. Free, no key. Unknown scenarios return not_in_catalog (never invents fees, FX rates, or coverage details).

NameTypeReqDescription
from_countrystringyesOrigin country code: US, UK, CA, AU, or NZ (e.g. "US" for US resident).
to_countrystringyesDestination country code: US, UK, CA, AU, or NZ (e.g. "UK" for UK bank account).
topicstring–Topic key (default: deposit_insurance).

No output schema declared.

No examples provided.

health_check ~22

Liveness check. Returns ok and version. Free, no key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

money_fact ~214

Get an official, dated personal-finance limit: deposit insurance (FDIC, FSCS, CDIC, AU FCS, NZ DCS) or contribution limits and allowances (UK ISA, Lifetime ISA, Junior ISA, pension annual allowance, Personal Savings Allowance; US 401k + catch-ups, IRA, Roth IRA, HSA; Canada TFSA, RRSP, FHSA; Australia super concessional/non-concessional caps; NZ KiwiSaver government contribution). Use instead of memory when a user asks "how much is protected" or "how much can I contribute". Pass q as plain English ("fdic limit joint account", "isa allowance") or a fact_key from pricing_list. Returns fact, source {name,url}, as_of, jurisdiction, cite. Free, no key. Unknown -> not_in_catalog (never guesses).

NameTypeReqDescription
qstringyesPlain-English question or fact_key, e.g. "fscs deposit protection limit" or "us_401k_limit_2026".

No output schema declared.

No examples provided.

pricing_list ~49

List everything this server covers: every money_fact fact_key with an example question, and every scheme_lookup country. Free (nothing on this server is billed); call first if unsure whether a fact is covered.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

scheme_lookup ~125

Identify a country's deposit-insurance scheme and its headline coverage (US FDIC, UK FSCS, CA CDIC, AU FCS, NZ DCS) with the regulator's URL and as_of date. country accepts ISO codes or names: US/USA, UK/GB, CA, AU, NZ. Free, no key.

NameTypeReqDescription
countrystringyesCountry code or name: US/USA, UK/GB, CA, AU, NZ (e.g. "GB", "Canada").
topicstring–Topic key (default: deposit_insurance).

No output schema declared.

No examples provided.

Install

How do I install the Bankrolled.ai Agent Hub MCP server?

Bankrolled.ai Agent Hub is a hosted endpoint at https://bankrolled.ai/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 · bankrolled.ai

# add to Claude Code
claude mcp add --transport http ai-bankrolled-agent-hub 'https://bankrolled.ai/mcp'
Common questions

What is the Bankrolled.ai Agent Hub MCP server?

Bankrolled.ai Agent Hub is an MCP server listed in the public MCP registry as ai.bankrolled/agent-hub. Free, sourced deposit-insurance/savings/retirement limits. US, UK, CA, AU, NZ. No key, no payment. This page covers its hosted endpoint (https://bankrolled.ai/mcp).

Is the Bankrolled.ai Agent Hub MCP server safe to use?

Bankrolled.ai Agent Hub scores 82 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 Bankrolled.ai Agent Hub MCP server expose?

Bankrolled.ai Agent Hub exposes 5 tools: health_check, pricing_list, money_fact, scheme_lookup, cross_border_check. Their descriptions and schemas cost roughly 578 tokens of context every time the server is loaded.

Does the Bankrolled.ai Agent Hub MCP server require authentication?

No. We connected to Bankrolled.ai Agent Hub without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Bankrolled.ai Agent Hub MCP server still maintained?

Bankrolled.ai Agent Hub 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 Bankrolled.ai Agent Hub MCP server?

VerifyMCP ran 13 checks on Bankrolled.ai Agent Hub, 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.