Remote MCP · Endpoint

LLM Broker MCP server

No. LLM Broker answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.llm-broker.net/api/v1/broker/mcp

The last check completed an MCP handshake.

Registry name
net.llm-broker/broker
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
288 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
One key, every model: measured scores and live prices, routed per request to the cheapest fit.
Listing
From the official MCP registry (active).
Recent checks of LLM Broker
CheckedResultHandshake
1 hour agoHandshake completed288 ms
3 days agoHandshake completed293 ms
13 days agoHandshake completed327 ms
14 days agoHandshake completed307 ms
15 days agoHandshake completed314 ms
16 days agoHandshake completed419 ms
18 days agoHandshake completed293 ms
18 days agoHandshake completed297 ms
19 days agoHandshake completed293 ms
21 days agoHandshake completed296 ms
22 days agoHandshake completed287 ms
25 days agoHandshake completed289 ms
27 days agoHandshake completed290 ms
30 days agoHandshake completed296 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 24 responding of 24.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with LLM Broker and makes no claim about it beyond what these checks measured.