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.

com.brokerchooser/broker-safety

REMOTE · MCP.BROKERCHOOSER.COM

MCP server offering regulator-sourced legitimacy checks on investment entities by name or URL.

−16 this week 64 Trust /100

Last scanned (23 hours ago)

Scores higher than 46% 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 enforcement could not be verified: the plaintext port answered with HTTP 403, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • 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 Usability60
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 477 tokens (~238/item across 2 items; 2 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 Management0
  • Stability check failed: schema churn in the 30 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 2 additions. See how to fix → Fail
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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 (12)

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

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 403, which proves neither a plaintext path nor enforcement.

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.

  • 18 Nov 26 −16
    • Stability: pass → fail ▼ security
    • A breaking change shipped without a version bump: still 1.0.0 ▼ security
    • Tool “is-broker-scam-tool” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 362 → 238 ▲ functional
    • Schema quality: excellent → good functional
    • New tool “is-broker-available-in-country-tool” functional
    • New tool “is-broker-trusted” functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • 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
  • 28 Sept 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
  • 25 Sept 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
  • 22 Sept 26 0
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • MCP protocol version: 2025-11-25 → 2026-07-28 functional
  • 26 Aug 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
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://mcp.brokerchooser.com/servers/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=brokerchooser.com CN=WE1,O=Google Trust Services,C=US 10 Nov 2026 8 Feb 2027 ECDSA 256 ECDSA-SHA256 8d3af2c0db7068d913e7c6a8af9044cc
SANs: brokerchooser.com, *.brokerchooser.com
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 mcp.brokerchooser.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
brokerchooser.com. 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
x-content-type-options nosniff
x-frame-options SAMEORIGIN

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.brokerchooser.com/servers/mcp Verified 200
http (plaintext) http://mcp.brokerchooser.com/servers/mcp Inconclusive 403
MCP tools · 2 exposed · ~429 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
is-broker-available-in-country-tool ~244

Tells whether a broker accepts clients from a given country, for brokers reviewed by BrokerChooser. Brokers are licensed per jurisdiction, so a broker that is safe and well regulated can still be unusable to someone who cannot open an account with it. The country is a required input; this tool has no way of detecting where the user is located.

NameTypeReqDescription
countrystringyesThe country the user lives in, as its ISO 3166-1 alpha-2 code (e.g., 'de' for Germany, 'gb' for the United Kingdom). The English country name ('Germany') is also accepted. Regions such as 'Europe' ar…
querystringyesA string containing either the broker's company name OR the broker's website domain as provided by the user. If providing a website, use only the domain name with TLD (e.g., 'example.com' not 'https:…

No output schema declared.

No examples provided.

is-broker-trusted ~185

Retrieves information to determine whether a broker is legitimate or a scam. This tool can look up brokers using either their company name or website URL. It returns verification data, scam reports, regulatory status, and trustworthiness indicators to help assess the broker's credibility. Use this tool when users ask about broker reliability, safety, legitimacy, or want to verify if a specific broker is trustworthy before investing or trading.

NameTypeReqDescription
querystringyesA string containing either the broker's company name OR the broker's website domain as provided by the user. If providing a website, use only the domain name with TLD (e.g., 'example.com' not 'https:…

No output schema declared.

No examples provided.

Install

How do I install the com.brokerchooser/broker-safety MCP server?

com.brokerchooser/broker-safety is a hosted endpoint at https://mcp.brokerchooser.com/servers/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 · mcp.brokerchooser.com

# add to Claude Code
claude mcp add --transport http com-brokerchooser-broker-safety 'https://mcp.brokerchooser.com/servers/mcp'
Common questions

What is the com.brokerchooser/broker-safety MCP server?

com.brokerchooser/broker-safety is an MCP server listed in the public MCP registry as com.brokerchooser/broker-safety. MCP server offering regulator-sourced legitimacy checks on investment entities by name or URL. This page covers its hosted endpoint (https://mcp.brokerchooser.com/servers/mcp).

Is the com.brokerchooser/broker-safety MCP server safe to use?

com.brokerchooser/broker-safety scores 64 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 com.brokerchooser/broker-safety MCP server expose?

com.brokerchooser/broker-safety exposes 2 tools: is-broker-trusted, is-broker-available-in-country-tool. Their descriptions and schemas cost roughly 429 tokens of context every time the server is loaded.

Does the com.brokerchooser/broker-safety MCP server require authentication?

No. We connected to com.brokerchooser/broker-safety without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.brokerchooser/broker-safety MCP server still maintained?

com.brokerchooser/broker-safety 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 com.brokerchooser/broker-safety MCP server?

VerifyMCP ran 12 checks on com.brokerchooser/broker-safety, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about com.brokerchooser/broker-safety: HTTPS. 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.