Remote MCP · Endpoint

LLM Pricing MCP server

No. LLM Pricing answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://llm-pricing-api.fly.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.skakumanu/llm-pricing-mcp-server
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
860 ms
Tools exposed
32 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Real-time, drift-verified LLM pricing across 31 providers with cost+quality model routing.
Listing
From the official MCP registry (active).
Recent checks of LLM Pricing
CheckedResultHandshake
34 minutes agoHandshake completed860 ms
8 days agoHandshake completed40 ms
9 days agoHandshake completed81 ms
11 days agoHandshake completed80 ms
12 days agoHandshake completed80 ms
12 days agoHandshake completed99 ms
14 days agoHandshake completed73 ms
14 days agoHandshake completed73 ms
16 days agoHandshake completed76 ms
19 days agoHandshake completed91 ms
21 days agoHandshake completed85 ms
24 days agoHandshake completed123 ms
26 days agoHandshake completed66 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 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 LLM Pricing and makes no claim about it beyond what these checks measured.