Remote MCP · Endpoint

Cheapest LLM API MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://cheapestllmapi.com/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.github.tehtelabs/cheapestllmapi
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
12 tools
Uptime, last 30 days
76.9% from 13 checks
Described by its publisher as
Compare LLM API prices, search models and providers, and access reviewed benchmark results.
Listing
From the official MCP registry (active).
Recent checks of Cheapest LLM API
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
7 days agoHandshake completed853 ms
9 days agoHandshake completed1.13 s
11 days agoHandshake completed892 ms
13 days agoHandshake completed1.26 s
15 days agoHandshake completed373 ms
17 days agoHandshake completed317 ms
19 days agoHandshake completed466 ms
20 days agoHandshake completed606 ms
21 days agoHandshake completed385 ms
23 days agoHandshake completed541 ms

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

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 Cheapest LLM API and makes no claim about it beyond what these checks measured.