Remote MCP · Endpoint

FitLLM MCP server

No. FitLLM answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://fitllm.run/api/mcp

The last check completed an MCP handshake.

Registry name
run.fitllm/fitllm
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.14 s
Tools exposed
3 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Will this LLM fit on your GPU, multi-GPU rig or Mac? Exact VRAM & KV-cache math. Read-only.
Listing
From the official MCP registry (active).
Recent checks of FitLLM
CheckedResultHandshake
1 hour agoHandshake completed1.14 s
2 days agoHandshake completed87 ms
4 days agoHandshake completed134 ms
5 days agoHandshake completed73 ms
7 days agoHandshake completed57 ms
8 days agoHandshake completed112 ms
9 days agoHandshake completed94 ms
12 days agoHandshake completed68 ms
13 days agoHandshake completed102 ms
15 days agoHandshake completed69 ms
17 days agoHandshake completed74 ms
18 days agoHandshake completed122 ms
19 days agoHandshake completed118 ms
20 days agoHandshake completed65 ms
21 days agoHandshake completed88 ms
21 days agoHandshake completed74 ms
23 days agoHandshake completed93 ms

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

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