Remote MCP · Endpoint

LLM Configurator MCP server

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

UpLast checked 1 hour ago

Server URL

https://elgadmisijrfowuujcmu.supabase.co/functions/v1/mcp

The last check completed an MCP handshake.

Registry name
io.github.aikuba/llmconfigurator
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
321 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read-only: which local LLMs a GPU or Mac can run - VRAM fit, tokens/sec, model specs.
Listing
From the official MCP registry (active).
Recent checks of LLM Configurator
CheckedResultHandshake
1 hour agoHandshake completed321 ms
2 days agoHandshake completed382 ms
5 days agoHandshake completed215 ms
7 days agoHandshake completed459 ms
9 days agoHandshake completed728 ms
11 days agoHandshake completed432 ms
13 days agoHandshake completed380 ms
15 days agoHandshake completed290 ms
17 days agoHandshake completed279 ms
19 days agoHandshake completed320 ms
20 days agoHandshake completed328 ms
21 days agoHandshake completed272 ms
23 days agoHandshake completed403 ms
25 days agoHandshake completed258 ms

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

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