LLM Broker
REMOTE · API.LLM-BROKER.NET
One key, every model: measured scores and live prices, routed per request to the cheapest fit.
Available components
Last scanned (5 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 17 Oct 2026.
Category AI and Machine Learning
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
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 929 tokens (~116/item across 8 items; 8 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 Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage77
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 32% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "chat" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 9 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
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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 27. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 +2
- MCP protocol: fail → pass ▲ functional
- 6 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: pass → fail ▼ functional
- Server version: 1.1.0 → 1.2.0 functional
- New tool “create_account” functional
- New tool “report_outcome” functional
- 3 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- Tool “list_models” rewrote its description, which is the text the model reads security
- Schema quality: 131 → 147 ▼ functional
- Tool coverage: 22% → 32% ▲ functional
- Schema quality: 131 → 103 ▲ functional
- Tool coverage: 22% → 30% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “estimate_cost” functional
- New tool “get_balance” functional
- New tool “get_model” functional
- New tool “recommend_model” functional
- “list_models” added an optional parameter “currency” cosmetic
- “list_models” reworded the description of “max_price_per_mtok” cosmetic
- 2 Oct 26 60
First indexed and scored.
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 17 Oct 2026 · Probed https://api.llm-broker.net/api/v1/broker/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.llm-broker.net | CN=YR2,O=Let's Encrypt,C=US | 2 Oct 2026 | 31 Dec 2026 | RSA 2048 | SHA256-RSA | 5782662b06947302624fb3e92b86c61735a |
| SANs: api.llm-broker.net | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.llm-broker.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| llm-broker.net. | 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; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.llm-broker.net/api/v1/broker/mcp | Verified | 200 | |
| http (plaintext) | http://api.llm-broker.net/api/v1/broker/mcp | HTTPS enforced | 308 | https://api.llm-broker.net/api/v1/broker/mcp |
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 →
chat Run a chat completion through the broker ~119
Sends messages to the broker (OpenAI chat completions). model defaults to `taylor` (strongest measured model); any id from list_models works. routing sets criteria per request, e.g. {"category": "coding", "level": "best"}. Needs Authorization: Bearer ast_sk_… — billed like the REST API.
| Name | Type | Req | Description |
|---|---|---|---|
| max_tokens | integer | – | – |
| messages | array | – | – |
| model | string | – | – |
| prompt | string | – | Shortcut for a single user message |
| routing | object | – | – |
No output schema declared.
No examples provided.
create_account Buy an API key ~170
Creates a card checkout (Stripe) for a new broker account — same as POST /api/v1/broker/accounts. Give checkout_url to your human; after payment the API key is shown exactly once at status_url (GET, poll until 200). topup: amount 10/25/50, monthly: limit 50/100/250 (USD/EUR/CHF; other currencies: GET /api/v1/broker/currencies). Omit category and level to choose per request.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | integer | – | topup amount in currency |
| billing | string | yes | – |
| category | string | – | optional, with level: a fixed performance promise |
| currency | string | – | – |
| level | string | – | – |
| limit | integer | – | monthly credit limit in currency |
No output schema declared.
No examples provided.
estimate_cost Estimate the cost of a request ~78
Cost estimate at list price for a model and token counts, in your currency. The bill follows the offer the router actually picks (broker.cost in the chat result).
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | ISO 4217, default USD |
| input_tokens | integer | – | – |
| model | string | yes | – |
| output_tokens | integer | – | – |
No output schema declared.
No examples provided.
get_balance Account balance and spend ~40
Balance, credit limit and spend this month (CHF, the book currency), billing mode and payment currency of the account behind Authorization: Bearer ast_sk_….
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_model Get one model with scores and prices ~58
One model from list_models by id: measured scores per category, price per 1M tokens (default USD), regions, context and capabilities.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | ISO 4217, default USD |
| id | string | yes | – |
No output schema declared.
No examples provided.
list_models List models with measured scores and prices ~129
Models on the broker with benchmark scores per category (0–1, measured by us), price per 1M tokens (default USD, any currency from GET /api/v1/broker/currencies) and regions. Filter by category, region and price; sorted by score in the category, else by price.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| currency | string | – | ISO 4217 code, default USD |
| limit | integer | – | – |
| max_price_per_mtok | number | – | Max output price per 1M tokens, in currency |
| region | string | – | – |
No output schema declared.
No examples provided.
recommend_model Recommend a model for a task ~130
Picks from the published catalog (our own benchmark scores, list prices): best = highest score in the category, best_value = score per output price, plus alternatives. Only measured models are recommended. Returns chat_arguments for that model and a routing object to let the broker pick per request.
| Name | Type | Req | Description |
|---|---|---|---|
| capabilities | array | – | – |
| category | string | yes | – |
| currency | string | – | ISO 4217, default USD |
| max_price_per_mtok | number | – | Max output price per 1M tokens, in currency |
| min_score | number | – | – |
| region | string | – | – |
No output schema declared.
No examples provided.
report_outcome Report whether a request did its job ~94
Tell the broker if the answer to a request worked for your task — request_id comes from broker.receipt of every chat answer. Outcomes appear per model in list_models as reported (failures_30d / outcomes_30d), so the scores are checked against real tasks. No refund, no price change.
| Name | Type | Req | Description |
|---|---|---|---|
| outcome | string | yes | – |
| reason | string | – | – |
| request_id | string | yes | – |
No output schema declared.
No examples provided.
How do I install the LLM Broker MCP server?
LLM Broker is a hosted endpoint at https://api.llm-broker.net/api/v1/broker/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 · api.llm-broker.net
claude mcp add --transport http net-llm-broker-broker 'https://api.llm-broker.net/api/v1/broker/mcp'
What is the LLM Broker MCP server?
LLM Broker is an MCP server listed in the public MCP registry as net.llm-broker/broker. One key, every model: measured scores and live prices, routed per request to the cheapest fit. This page covers its hosted endpoint (https://api.llm-broker.net/api/v1/broker/mcp).
Is the LLM Broker MCP server safe to use?
LLM Broker 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 LLM Broker MCP server expose?
LLM Broker exposes 8 tools: list_models, get_model, recommend_model, estimate_cost, chat, and 3 more. Their descriptions and schemas cost roughly 818 tokens of context every time the server is loaded.
Does the LLM Broker MCP server require authentication?
No. We connected to LLM Broker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the LLM Broker MCP server still maintained?
LLM Broker is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.