# LEEVAR reliability battery (mcpb · leevar-mcp-0.1.0.mcpb)

Grade an AI agent's transcripts on 18 reliability tests. Thin evidence is NOT TESTED, not guessed.

- Trust score: 62/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- mcpb · `leevar-mcp-0.1.0.mcpb`: 62/100 (this document), [markdown](https://verifymcp.io/servers/forevercrab321-svg-leevar/leevar-mcp.md), [page](https://verifymcp.io/servers/forevercrab321-svg-leevar/leevar-mcp)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/forevercrab321-svg/leevar-battery/releases/download/v0.1.0/leevar-mcp-0.1.0.mcpb`
- Transport: `stdio`
- SHA-256: `e4d79b50a6d3bb32268c08b71b0bda06d352c4ba40e4ba41f8ac111fe592760d`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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.

- **Supply Chain Security**: 23/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs were checked across the 92 of 92 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 39 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 426 tokens (~142/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**: 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 3 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 LEEVAR reliability battery MCP server?

LEEVAR reliability battery ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, e4d79b50a6d3bb32268c08b71b0bda06d352c4ba40e4ba41f8ac111fe592760d; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/forevercrab321-svg/leevar-battery/releases/download/v0.1.0/leevar-mcp-0.1.0.mcpb`
- SHA-256: `e4d79b50a6d3bb32268c08b71b0bda06d352c4ba40e4ba41f8ac111fe592760d`

### Verify on macOS / Linux

```bash
echo "e4d79b50a6d3bb32268c08b71b0bda06d352c4ba40e4ba41f8ac111fe592760d  leevar-mcp-0.1.0.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\leevar-mcp-0.1.0.mcpb).Hash -eq "e4d79b50a6d3bb32268c08b71b0bda06d352c4ba40e4ba41f8ac111fe592760d"
```

## 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-05 (score 62, 0)

- [security] Stability: 0.97 → pass

### 2026-11-04 (score 62, +1)

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

### 2026-11-03 (score 61, −1)

- [functional] Stability: pass → 0.93

### 2026-10-28 (score 62, 0)

- [security] Stability: 0.97 → pass

### 2026-10-27 (score 62, +1)

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

### 2026-10-25 (score 61, +1)

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

### 2026-10-23 (score 60, +1)

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

### 2026-10-21 (score 59, +1)

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

## MCP tools (3)

### `leevar_scan_transcript` (~286 tokens)

Scan an AI agent's transcripts

Send real conversation samples from an AI agent to the LEEVAR reliability battery (18 tests, 6 dimensions). Free: 5 scans a month per email, no account. Returns a scan id; the result takes a few minutes — read it with leevar_scan_status. Dimensions the samples cannot evidence come back NOT TESTED, and with fewer than two thirds of the gradeable tests evidenced no grade is issued. Samples go to LEEVAR's hosted service, are graded there by third-party language models (named at https://www.leevar.live/privacy), and are deleted 30 days after the scan; strip keys, credentials and personal data first. Each scan uses one of the email's 5 free monthly scans. Ask the user before sending their data.

Input parameters:

- `agent_name` (string, required): Name of the agent being graded
- `agent_type` (string): e.g. Customer support, Coding, Research
- `description` (string): What the agent does, in a sentence or two
- `email` (string, required): Where the report goes; also the free-quota key and needed to read the result
- `model` (string): Model class the agent runs on
- `transcripts` (array, required): 1–8 real conversation samples, e.g. 'User: …\nAgent: …'. More, longer samples evidence more tests.

### `leevar_scan_status` (~93 tokens)

Read a LEEVAR scan result

Read the result of a scan started with leevar_scan_transcript: status, grade (only when one was issued), coverage, and the written report. A missing grade means the evidence was too thin to grade — never treat it as a pass.

Input parameters:

- `email` (string, required): The email the scan was created with
- `scan_id` (string, required): e.g. SCN-2026-1234

### `leevar_battery` (~47 tokens)

List the 18 reliability tests

The LEEVAR battery: 6 dimensions × 3 tests, what each test checks and the failure it catches. Use it to pick conversation samples that exercise every test before scanning.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/forevercrab321-svg-leevar/leevar-mcp#diagnostics

## Score history

- 2026-11-05: 62
- 2026-11-04: 62
- 2026-11-03: 61
- 2026-11-02: 62
- 2026-11-01: 62
- 2026-10-31: 62
- 2026-10-30: 62
- 2026-10-29: 62
- 2026-10-28: 62
- 2026-10-27: 62
- 2026-10-26: 61
- 2026-10-25: 61
- 2026-10-24: 60
- 2026-10-23: 60
- 2026-10-22: 59
- 2026-10-21: 59
- 2026-10-20: 58
- 2026-10-19: 58
- 2026-10-18: 57
- 2026-10-17: 57
- 2026-10-16: 56
- 2026-10-15: 56
- 2026-10-14: 55
- 2026-10-13: 55
- 2026-10-12: 55
- 2026-10-10: 54
- 2026-10-05: 48
- 2026-10-04: 48
- 2026-10-03: 48
- 2026-10-02: 48

## Common questions

### What is the LEEVAR reliability battery MCP server?

LEEVAR reliability battery is an MCP server listed in the public MCP registry as io.github.forevercrab321-svg/leevar. Grade an AI agent's transcripts on 18 reliability tests. Thin evidence is NOT TESTED, not guessed. This page covers its MCPB bundle (https://github.com/forevercrab321-svg/leevar-battery/releases/download/v0.1.0/leevar-mcp-0.1.0.mcpb).

### Is the LEEVAR reliability battery MCP server safe to use?

LEEVAR reliability battery scores 62 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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 LEEVAR reliability battery MCP server expose?

LEEVAR reliability battery exposes 3 tools: leevar_scan_transcript, leevar_scan_status, leevar_battery. Their descriptions and schemas cost roughly 426 tokens of context every time the server is loaded.

### What licence is the LEEVAR reliability battery MCP server under?

LEEVAR reliability battery declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/forevercrab321-svg/leevar-battery
- Website: https://www.leevar.live/clinic
- Changelog RSS feed: https://verifymcp.io/servers/forevercrab321-svg-leevar/leevar-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/forevercrab321-svg-leevar/leevar-mcp.json
- HTML version of this page: https://verifymcp.io/servers/forevercrab321-svg-leevar/leevar-mcp