# Clearbar model verdicts (remote · clearbar.grain64.com)

Cheapest LLM that passes each task: cost per successful task and pass rate on public datasets.

- Trust score: 74/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `clearbar.grain64.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-grain64-clearbar/clearbar.md), [page](https://verifymcp.io/servers/com-grain64-clearbar/clearbar)

## Channel facts

- Endpoint: `https://clearbar.grain64.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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-21.

- **Endpoint Security**: 74/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.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 662 tokens (~220/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 Clearbar model verdicts MCP server?

Clearbar model verdicts is a hosted endpoint at https://clearbar.grain64.com/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 com-grain64-clearbar 'https://clearbar.grain64.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-grain64-clearbar": {
      "url": "https://clearbar.grain64.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-grain64-clearbar": {
      "type": "http",
      "url": "https://clearbar.grain64.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-grain64-clearbar]
url = "https://clearbar.grain64.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-grain64-clearbar": {
      "type": "remote",
      "url": "https://clearbar.grain64.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-grain64-clearbar --url 'https://clearbar.grain64.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-grain64-clearbar:
    url: "https://clearbar.grain64.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-grain64-clearbar": {
      "Transport": "http",
      "Url": "https://clearbar.grain64.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-grain64-clearbar -t streamable-http -u 'https://clearbar.grain64.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-grain64-clearbar": {
      "type": "http",
      "url": "https://clearbar.grain64.com/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-21 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 73, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 449 → 662
- [functional] Server version: 1.2.0 → 1.3.0
- [functional] New tool “cheapest_model”

### 2026-11-18 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 72, −1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_verdict” rewrote its description, which is the text the model reads
- [security] Tool “list_verdicts” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional] Server version: 1.1.0 → 1.2.0
- [cosmetic] “get_verdict” added an optional parameter “task”
- [cosmetic] “get_verdict” reworded the description of “slug”
- [cosmetic] “get_verdict” made “slug” optional

### 2026-11-15 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-13 (score 72)

First indexed and scored.

## MCP tools (3)

### `cheapest_model` (~159 tokens)

Cheapest model that still passes, per task, in one call

One call, the headline answer: which is the cheapest LLM that still passes? With no arguments you get every task family (classification, extraction, tool-call) with its cheapest passing model, cost per successful task in US dollars (retries and failures counted), how much cheaper it is than the baseline, and the verdict page that proves it. Pass {"task":"spam detection"} (plain words, or a family such as classification) for just that answer. Next call: get_verdict with the slug for the full candidate table, failures and the re-run script.

Input parameters:

- `task` (string): Optional. The task in plain words (spam detection, sentiment, json extraction, tool calling) or a family: classification, extraction, tool-call.

Output parameters:

- `answers` (array)
- `app_note` (string)
- `app_url` (string): Where to run the same verdict on your own examples.
- `count` (integer): Number of answers returned.
- `headline` (string): The overview in one or two sentences.
- `next_call` (string): The call to make next for the full table of one verdict.
- `prices_as_of` (string|null): Date (YYYY-MM-DD) of the newest price snapshot behind the figures.

### `list_verdicts` (~115 tokens)

List verdicts: which model is cheapest for each task

Which LLM is the cheapest that still passes? Lists every published Clearbar verdict at once: the task, the pass bar, the cheapest passing model, its cost per successful task (retries and failures counted) and the page to check it. Optional filter by task type. Next call: get_verdict with {"task":"spam detection"} (or a slug from this list) for the full table.

Input parameters:

- `task` (string): Only verdicts of this task type, for example classification, extraction or tool-call.

Output parameters:

- `app_note` (string)
- `app_url` (string): Where to run the same verdict on your own examples.
- `count` (integer): Number of verdicts returned.
- `next_call` (string): The call to make next for the full table of one verdict.
- `prices_as_of` (string|null): Date (YYYY-MM-DD) of the newest price snapshot behind the figures.
- `verdicts` (array)

### `get_verdict` (~192 tokens)

Get one verdict: cheapest passing model, cost, failures

Answers: which is the cheapest LLM that still passes for <task>? Give the task in plain words (for example "spam detection", "sentiment", "json extraction", "tool calling", "intent classification") or a verdict slug, and get the cheapest model that clears the bar, its pass rate and cost per successful task in US dollars, the baseline it is compared with, every candidate's status, plus links to the verdict page, the run file (JSON) and the script that re-runs it. Example: {"task":"spam detection"} returns the sms-spam verdict. Not sure what exists? Call list_verdicts first.

Input parameters:

- `slug` (string): Or the exact verdict slug from list_verdicts, for example sms-spam.
- `task` (string): The task in plain words, for example spam detection, sentiment, json extraction. The closest published verdict answers.

Output parameters:

- `answer` (string): One-sentence verdict in plain words, with the price date.
- `app_note` (string)
- `app_url` (string)
- `baseline_cost_per_successful_task_usd` (number|null)
- `baseline_model` (string|null)
- `baseline_pass_rate` (number|null)
- `candidates` (array)
- `cheapest_passing_model` (string|null): The cheapest model that clears the bar; null when none does.
- `cost_per_successful_task_usd` (number|null): US dollars per successful task, retries and failures counted.
- `dataset` (object): Public dataset behind the run: name, rows, source, licence.
- `matched_by` (string): How the verdict was chosen: the exact slug, or the closest published verdict to the task you described.
- `pass_bar` (number): Pass-rate threshold the cheapest model has to clear (0 to 1).
- `pass_rate` (number|null)
- `price_snapshot_at` (string|null)
- `ran_at` (string|null)
- `rerun_script_url` (string|null): Script that re-runs the verdict; null when none is published.
- `run_file_url` (string): The run file (JSON) to check the figures.
- `saving_pct` (number|null)
- `slug` (string): Verdict slug, the key for get_verdict.
- `task` (string): Task type, for example classification.
- `title` (string)
- `verdict_kind` (string): switch (a cheaper model passes) or keep (the baseline is already cheapest).
- `verdict_url` (string): The verdict page, with the evidence.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-grain64-clearbar/clearbar#diagnostics

## Score history

- 2026-11-21: 74
- 2026-11-20: 73
- 2026-11-19: 73
- 2026-11-18: 73
- 2026-11-17: 72
- 2026-11-16: 72
- 2026-11-15: 73
- 2026-11-14: 72
- 2026-11-13: 72

## Common questions

### What is the Clearbar model verdicts MCP server?

Clearbar model verdicts is an MCP server listed in the public MCP registry as com.grain64/clearbar. Cheapest LLM that passes each task: cost per successful task and pass rate on public datasets. This page covers its hosted endpoint (https://clearbar.grain64.com/mcp).

### Is the Clearbar model verdicts MCP server safe to use?

Clearbar model verdicts scores 74 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 Clearbar model verdicts MCP server expose?

Clearbar model verdicts exposes 3 tools: cheapest_model, list_verdicts, get_verdict. Their descriptions and schemas cost roughly 466 tokens of context every time the server is loaded.

### Does the Clearbar model verdicts MCP server require authentication?

No. We connected to Clearbar model verdicts without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Clearbar model verdicts MCP server still maintained?

Clearbar model verdicts is still listed as active in the MCP registry. We last reached this channel on 21 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 Clearbar model verdicts MCP server?

VerifyMCP ran 13 checks on Clearbar model verdicts, 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://clearbar.grain64.com/mcp
- Website: https://clearbar.grain64.com/docs/#mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-grain64-clearbar/clearbar.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-grain64-clearbar/clearbar/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-grain64-clearbar/clearbar.json
- HTML version of this page: https://verifymcp.io/servers/com-grain64-clearbar/clearbar
