# LLM Configurator (remote · elgadmisijrfowuujcmu.supabase.co)

Read-only: which local LLMs a GPU or Mac can run - VRAM fit, tokens/sec, model specs.

- Trust score: 88/100 (high trust)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `elgadmisijrfowuujcmu.supabase.co`: 88/100 (this document), [markdown](https://verifymcp.io/servers/aikuba-llmconfigurator/functions-v1-mcp.md), [page](https://verifymcp.io/servers/aikuba-llmconfigurator/functions-v1-mcp)

## Channel facts

- Endpoint: `https://elgadmisijrfowuujcmu.supabase.co/functions/v1/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http aikuba-llmconfigurator 'https://elgadmisijrfowuujcmu.supabase.co/functions/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "aikuba-llmconfigurator": {
      "url": "https://elgadmisijrfowuujcmu.supabase.co/functions/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "aikuba-llmconfigurator": {
      "type": "http",
      "url": "https://elgadmisijrfowuujcmu.supabase.co/functions/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.aikuba-llmconfigurator]
url = "https://elgadmisijrfowuujcmu.supabase.co/functions/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "aikuba-llmconfigurator": {
      "type": "remote",
      "url": "https://elgadmisijrfowuujcmu.supabase.co/functions/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add aikuba-llmconfigurator --url 'https://elgadmisijrfowuujcmu.supabase.co/functions/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  aikuba-llmconfigurator:
    url: "https://elgadmisijrfowuujcmu.supabase.co/functions/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "aikuba-llmconfigurator": {
      "Transport": "http",
      "Url": "https://elgadmisijrfowuujcmu.supabase.co/functions/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add aikuba-llmconfigurator -t streamable-http -u 'https://elgadmisijrfowuujcmu.supabase.co/functions/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "aikuba-llmconfigurator": {
      "type": "http",
      "url": "https://elgadmisijrfowuujcmu.supabase.co/functions/v1/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-01 (score 88, +1)

- [security] Stability: 0.97 → pass

### 2026-10-30 (score 87, +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.

### 2026-10-28 (score 86, +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.

### 2026-10-26 (score 85, +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.

### 2026-10-24 (score 84, +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.

### 2026-10-22 (score 83, +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.

### 2026-10-20 (score 82, +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.

### 2026-10-17 (score 81, +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.

## MCP tools (5)

### `search_catalog` (~144 tokens)

Find hardware or a model

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.

Input parameters:

- `kind` (string, required): Search hardware or models. Required.
- `limit` (integer): Maximum matches, 1 to 10. Default 5.
- `query` (string, required): Hardware or model name as the user wrote it, e.g. "4090", "m4 max 64", "llama 3.3 70b".

Output parameters:

- `data_as_of` (string): Date the bundled catalogue was last updated. Not the time of this call.
- `kind` (string)
- `matches` (array)
- `summary` (string): One or two plain-language sentences stating the answer.

### `check_hardware_fit` (~197 tokens)

Check whether a model fits hardware

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.

Input parameters:

- `context_length` (integer): Context window in tokens that the KV cache is sized for. 512 to 262144. Default 4096.
- `hardware_id` (string, required): Hardware id from search_catalog.
- `model_id` (string, required): 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.

Output parameters:

- `context_length` (integer)
- `data_as_of` (string): Date the bundled catalogue was last updated. Not the time of this call.
- `hardware` (object)
- `memory` (object): Memory arithmetic for the requested quantisation and context length.
- `model` (object)
- `notes` (array)
- `quantisation` (string)
- `sources` (array): Primary sources for the model and hardware records. May be empty.
- `speed`: null when the model does not fit, because a speed for hardware that cannot load the weights would be invented.
- `summary` (string): One or two plain-language sentences stating the answer.
- `url` (string)
- `verdict` (string)

### `models_for_hardware` (~236 tokens)

List models a machine can run

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.

Input parameters:

- `context_length` (integer): Context window in tokens that the KV cache is sized for. 512 to 262144. Default 4096.
- `hardware_id` (string, required): 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.

Output parameters:

- `context_length` (integer)
- `data_as_of` (string): Date the bundled catalogue was last updated. Not the time of this call.
- `hardware` (object)
- `models` (array)
- `quantisation` (string)
- `summary` (string): One or two plain-language sentences stating the answer.
- `url` (string)
- `use_case`: The use-case filter applied, or null.

### `compare_hardware` (~96 tokens)

Compare two to four machines

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.

Input parameters:

- `hardware_ids` (array, required): Two to four hardware ids from search_catalog.

Output parameters:

- `data_as_of` (string): Date the bundled catalogue was last updated. Not the time of this call.
- `hardware` (array)
- `summary` (string): One or two plain-language sentences stating the answer.

### `get_model_specs` (~90 tokens)

Get a model's specifications

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.

Input parameters:

- `model_id` (string, required): Model id from search_catalog.

Output parameters:

- `data_as_of` (string): Date the bundled catalogue was last updated. Not the time of this call.
- `model` (object)
- `quantisations` (array): Weight size per quantisation. Excludes KV cache and overhead, which depend on context length.
- `sources` (array)
- `summary` (string): One or two plain-language sentences stating the answer.
- `url` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/aikuba-llmconfigurator/functions-v1-mcp#diagnostics

## Score history

- 2026-11-05: 88
- 2026-11-04: 88
- 2026-11-03: 88
- 2026-11-02: 88
- 2026-11-01: 88
- 2026-10-31: 87
- 2026-10-30: 87
- 2026-10-29: 86
- 2026-10-28: 86
- 2026-10-27: 85
- 2026-10-26: 85
- 2026-10-25: 84
- 2026-10-24: 84
- 2026-10-23: 83
- 2026-10-22: 83
- 2026-10-21: 82
- 2026-10-20: 82
- 2026-10-19: 81
- 2026-10-18: 81
- 2026-10-17: 81
- 2026-10-16: 80
- 2026-10-15: 80
- 2026-10-14: 79
- 2026-10-13: 79
- 2026-10-12: 78
- 2026-10-10: 77
- 2026-10-09: 77
- 2026-10-06: 75
- 2026-10-04: 74
- 2026-10-03: 74

## Common questions

### 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.

## Links

- Remote endpoint: https://elgadmisijrfowuujcmu.supabase.co/functions/v1/mcp
- Repository: https://github.com/aikuba/LLMconfigurator.com
- Website: https://llmconfigurator.com/en/mcp
- Changelog RSS feed: https://verifymcp.io/servers/aikuba-llmconfigurator/functions-v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/aikuba-llmconfigurator/functions-v1-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/aikuba-llmconfigurator/functions-v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/aikuba-llmconfigurator/functions-v1-mcp