LLM Configurator
REMOTE · ELGADMISIJRFOWUUJCMU.SUPABASE.CO
Read-only: which local LLMs a GPU or Mac can run - VRAM fit, tokens/sec, model specs.
Available components
Last scanned (14 hours ago)
Scores higher than 96% of remote servers
Reachable. Last reached 5 Nov 2026.
Category AI and Machine Learning
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 838 tokens (~167/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://elgadmisijrfowuujcmu.supabase.co/functions/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=supabase.co | CN=WE1,O=Google Trust Services,C=US | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | d2b50611cd88e9c50e4e2231f4d3f059 |
| SANs: supabase.co, *.supabase.co | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of elgadmisijrfowuujcmu.supabase.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| co. | DS published | 7786 | 8 | Verified |
| supabase.co. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://elgadmisijrfowuujcmu.supabase.co/functions/v1/mcp | Verified | 200 | |
| http (plaintext) | http://elgadmisijrfowuujcmu.supabase.co/functions/v1/mcp | HTTPS enforced | 301 | https://elgadmisijrfowuujcmu.supabase.co/functions/v1/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_hardware_fit Check whether a model fits hardware ~197
Use this when the user asks whether one specific model runs on one specific machine, at what memory cost, and roughly how fast. Needs a hardware id and a model id from search_catalog. Returns a fit verdict, the memory arithmetic, and a decode-speed range with a confidence label. Memory is sized from all parameters, speed from active parameters. It does not recommend purchases and does not run anything.
| Name | Type | Req | Description |
|---|---|---|---|
| context_length | integer | – | Context window in tokens that the KV cache is sized for. 512 to 262144. Default 4096. |
| hardware_id | string | yes | Hardware id from search_catalog. |
| model_id | string | yes | Model id from search_catalog. |
| quantisation | string | – | Weight quantisation. One of Q2_K, Q3_K_M, Q4_K_M, Q5_K_M, Q6_K, Q8_0, F16. Default Q4_K_M. |
| Name | Type | Req | Description |
|---|---|---|---|
| context_length | integer | yes | – |
| data_as_of | string | yes | Date the bundled catalogue was last updated. Not the time of this call. |
| hardware | object | yes | – |
| memory | object | yes | Memory arithmetic for the requested quantisation and context length. |
| model | object | yes | – |
| notes | array | yes | – |
| quantisation | string | yes | – |
| sources | array | yes | Primary sources for the model and hardware records. May be empty. |
| speed | – | yes | null when the model does not fit, because a speed for hardware that cannot load the weights would be invented. |
| summary | string | yes | One or two plain-language sentences stating the answer. |
| url | string | yes | – |
| verdict | string | yes | – |
No examples provided.
compare_hardware Compare two to four machines ~96
Use this when the user compares two to four machines. Needs hardware ids from search_catalog. Returns memory, bandwidth, memory type, release year, status and a dated price where one is recorded, side by side. A price of null means none is on record. It does not check any model against the machines; use check_hardware_fit for that.
| Name | Type | Req | Description |
|---|---|---|---|
| hardware_ids | array | yes | Two to four hardware ids from search_catalog. |
| Name | Type | Req | Description |
|---|---|---|---|
| data_as_of | string | yes | Date the bundled catalogue was last updated. Not the time of this call. |
| hardware | array | yes | – |
| summary | string | yes | One or two plain-language sentences stating the answer. |
No examples provided.
get_model_specs Get a model's specifications ~90
Use this when the user asks about one model's size, architecture, context window or licence. Needs a model id from search_catalog. Returns total and active parameters, weight size per quantisation, context length, licence, release date and sources. It does not say whether the model fits any machine; use check_hardware_fit for that.
| Name | Type | Req | Description |
|---|---|---|---|
| model_id | string | yes | Model id from search_catalog. |
| Name | Type | Req | Description |
|---|---|---|---|
| data_as_of | string | yes | Date the bundled catalogue was last updated. Not the time of this call. |
| model | object | yes | – |
| quantisations | array | yes | Weight size per quantisation. Excludes KV cache and overhead, which depend on context length. |
| sources | array | yes | – |
| summary | string | yes | One or two plain-language sentences stating the answer. |
| url | string | yes | – |
No examples provided.
models_for_hardware List models a machine can run ~236
Use this when the user asks what models a given machine can run. Needs a hardware id from search_catalog. Returns up to 20 catalogue models ranked for that machine, each with a fit verdict and a speed range, optionally filtered to one use such as coding. It covers only models in the catalogue, at one quantisation and context length per call, and leaves out models that do not fit.
| Name | Type | Req | Description |
|---|---|---|---|
| context_length | integer | – | Context window in tokens that the KV cache is sized for. 512 to 262144. Default 4096. |
| hardware_id | string | yes | Hardware id from search_catalog. |
| limit | integer | – | Maximum models, 1 to 20. Default 10. |
| quantisation | string | – | Weight quantisation. One of Q2_K, Q3_K_M, Q4_K_M, Q5_K_M, Q6_K, Q8_0, F16. Default Q4_K_M. |
| use_case | string | – | Only list models tagged for this use. One of coding, chat, reasoning, agents, vision. Omit for all models. |
| Name | Type | Req | Description |
|---|---|---|---|
| context_length | integer | yes | – |
| data_as_of | string | yes | Date the bundled catalogue was last updated. Not the time of this call. |
| hardware | object | yes | – |
| models | array | yes | – |
| quantisation | string | yes | – |
| summary | string | yes | One or two plain-language sentences stating the answer. |
| url | string | yes | – |
| use_case | – | yes | The use-case filter applied, or null. |
No examples provided.
search_catalog Find hardware or a model ~144
Use this first when the user names a GPU, Mac, mini PC or language model and you need its id for the other tools. Matches names and common aliases in a fixed catalogue of local-LLM hardware and models. It does not return specs, fit or speed, and it does not search the web.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | Search hardware or models. Required. |
| limit | integer | – | Maximum matches, 1 to 10. Default 5. |
| query | string | yes | Hardware or model name as the user wrote it, e.g. "4090", "m4 max 64", "llama 3.3 70b". |
| Name | Type | Req | Description |
|---|---|---|---|
| data_as_of | string | yes | Date the bundled catalogue was last updated. Not the time of this call. |
| kind | string | yes | – |
| matches | array | yes | – |
| summary | string | yes | One or two plain-language sentences stating the answer. |
No examples provided.
How do I install the LLM Configurator MCP server?
LLM Configurator is a hosted endpoint at https://elgadmisijrfowuujcmu.supabase.co/functions/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · elgadmisijrfowuujcmu.supabase.co
claude mcp add --transport http aikuba-llmconfigurator 'https://elgadmisijrfowuujcmu.supabase.co/functions/v1/mcp'
What is the LLM Configurator MCP server?
LLM Configurator is an MCP server listed in the public MCP registry as io.github.aikuba/llmconfigurator. Read-only: which local LLMs a GPU or Mac can run - VRAM fit, tokens/sec, model specs. This page covers its hosted endpoint (https://elgadmisijrfowuujcmu.supabase.co/functions/v1/mcp).
Is the LLM Configurator MCP server safe to use?
LLM Configurator scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the LLM Configurator MCP server expose?
LLM Configurator exposes 5 tools: search_catalog, check_hardware_fit, models_for_hardware, compare_hardware, get_model_specs. Their descriptions and schemas cost roughly 763 tokens of context every time the server is loaded.
Does the LLM Configurator MCP server require authentication?
No. We connected to LLM Configurator without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the LLM Configurator MCP server still maintained?
LLM Configurator is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the LLM Configurator MCP server?
VerifyMCP ran 13 checks on LLM Configurator, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.