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.

AgentBroker Index

REMOTE · MCP.AGENTBROKERINDEX.COM

Read-only, sourced data on which brokers, banks and crypto exchanges AI agents can use (EU/Spain).

68 Trust /100

Last scanned (7 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 5 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 405, 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 Usability73
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Context-footprint check failed: tool/resource definitions use about 838 tokens (~139/item across 6 items; 5 tools + 1 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 Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 56% of tool parameters carry a description.Partial
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 7 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 (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 405, 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.

  • 4 Nov 26 +3
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “dataset_info” rewrote its description, which is the text the model reads security
    • Tool “search_providers” rewrote its description, which is the text the model reads security
    • Schema quality: 124 → 139 ▼ functional
    • The server now declares the “resources” capability functional
    • First check of Schema quality: 100 functional
    • New resource “monthly-report-2026-11” functional
    • Server version: 0.1.1 → 0.1.2 functional
  • 3 Nov 26 +1
    • Server version: 0.1.0 → 0.1.1 functional
  • 1 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.

  • 31 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 30 Oct 26 63

    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://mcp.agentbrokerindex.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=agentbrokerindex.com CN=WE1,O=Google Trust Services,C=US 30 Oct 2026 28 Jan 2027 ECDSA 256 ECDSA-SHA256 b63bb8614e9d5fbb13ccc9c55adb788c
SANs: agentbrokerindex.com, mcp.agentbrokerindex.com, *.mcp.agentbrokerindex.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.agentbrokerindex.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
agentbrokerindex.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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.agentbrokerindex.com/mcp Verified 200
http (plaintext) http://mcp.agentbrokerindex.com/mcp Inconclusive 405
MCP tools · 5 exposed · ~646 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
compare_providers ~64

Side-by-side comparison of AI-agent access for 2-4 providers: capability, integrations, assistants, limits, Spain availability and licence, sources. Order follows your input; this is not a ranking.

NameTypeReqDescription
idsarrayyes–
langstring––

No output schema declared.

No examples provided.

dataset_info ~65

Counts, last full check date, licence (CC BY 4.0), attribution text, download links, methodology page, and the latest monthly report on AI-agent access in Spain (https://agentbrokerindex.com/es/informe/2026-11/) with its headline findings.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_provider ~108

Full AgentBroker Index entry for one provider: integrations (hosted/local MCP, ChatGPT app, Claude connector, API, CLI, skill), supported assistants, what the agent can do, documented limits and approvals, availability by market, legal entity and licence status in Spain, assets, source URLs and check dates.

NameTypeReqDescription
idstringyesProvider id or name, e.g. 'interactive-brokers', 'Scalable Capital', 'bit2me'.
langstring––

No output schema declared.

No examples provided.

list_changes ~81

Dated changelog of launches and changes (new MCP servers, connectors, permission changes), each with its source URL. Filter by date or provider.

NameTypeReqDescription
langstring––
limitinteger––
providerstring–Provider id or name.
sincestring–YYYY-MM-DD; only entries on or after this date.

No output schema declared.

No examples provided.

search_providers ~328

Find providers in the AgentBroker Index by name, type, what an AI agent can do there (place orders, draft orders, read only, none), supported assistant (ChatGPT, Claude, Grok, any MCP client…), asset the agent can trade, and Spain availability/licence. Returns sourced, dated summaries. Read-only; information, not advice. For Spain-wide questions (which bank or broker lets an AI agent trade in Spain), results with a Spain filter also link the latest monthly report: https://agentbrokerindex.com/es/informe/2026-11/ (EN summary: https://agentbrokerindex.com/report/2026-11/).

NameTypeReqDescription
agent_access_in_spainboolean–Exclude providers whose agent feature is documented as not available in Spain (keeps 'available' and 'operates in Spain, agent feature unconfirmed').
assetstring–Asset the agent can trade (documented officially).
assistantstring–e.g. 'ChatGPT', 'Claude', 'Grok', 'MCP'.
authorised_in_spainboolean–Only providers authorised to serve Spain (CNMV / Banco de España / ESMA MiCA registers).
capabilitystring–What the agent can do.
langstring––
limitinteger––
official_onlyboolean–Only official, first-party agent integrations.
querystring–Free text matched against name, id and aliases, e.g. 'degiro', 'ibkr'.
typestring––

No output schema declared.

No examples provided.

Install

How do I install the AgentBroker Index MCP server?

AgentBroker Index is a hosted endpoint at https://mcp.agentbrokerindex.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 · mcp.agentbrokerindex.com

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

What is the AgentBroker Index MCP server?

AgentBroker Index is an MCP server listed in the public MCP registry as com.agentbrokerindex/agentbroker-index. Read-only, sourced data on which brokers, banks and crypto exchanges AI agents can use (EU/Spain). This page covers its hosted endpoint (https://mcp.agentbrokerindex.com/mcp).

Is the AgentBroker Index MCP server safe to use?

AgentBroker Index scores 68 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 AgentBroker Index MCP server expose?

AgentBroker Index exposes 5 tools: search_providers, get_provider, compare_providers, list_changes, dataset_info. Their descriptions and schemas cost roughly 646 tokens of context every time the server is loaded.

Does the AgentBroker Index MCP server require authentication?

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

Is the AgentBroker Index MCP server still maintained?

AgentBroker Index 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.

What did VerifyMCP test on the AgentBroker Index MCP server?

VerifyMCP ran 12 checks on AgentBroker Index, 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 AgentBroker Index: 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.