# LLM Assure (pypi · k11-llm-assure-mcp)

Red-team LLM apps: 41 OWASP LLM Top 10 probes, adaptive attacks, CI gate, audit reports.

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

## Components

- pypi · `k11-llm-assure-mcp`: 64/100 (this document), [markdown](https://verifymcp.io/servers/k11-software-solutions-llm-assure/k11-llm-assure-mcp.md), [page](https://verifymcp.io/servers/k11-software-solutions-llm-assure/k11-llm-assure-mcp)

## Channel facts

- Registry: `pypi`
- Package: `k11-llm-assure-mcp`
- Version: `0.1.0`
- Transport: `stdio`

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

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it.
  - 0 of 29 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to K11-Software-Solutions/k11techlab-llm-assurance-toolkit).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 535 tokens (~107/item across 5 items; 5 tools + 0 resources), lean.
  - 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**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_probe" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - 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 Assure MCP server?

LLM Assure runs locally as a PyPI package, launched with uvx k11-llm-assure-mcp. 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 k11-software-solutions-llm-assure -- uvx k11-llm-assure-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "k11-software-solutions-llm-assure": {
      "command": "uvx",
      "args": [
        "k11-llm-assure-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "k11-software-solutions-llm-assure": {
      "command": "uvx",
      "args": [
        "k11-llm-assure-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add k11-software-solutions-llm-assure -- uvx k11-llm-assure-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "k11-software-solutions-llm-assure": {
      "type": "local",
      "command": [
        "uvx",
        "k11-llm-assure-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add k11-software-solutions-llm-assure --command uvx --arg k11-llm-assure-mcp
```

### Hermes

```yaml
mcp_servers:
  k11-software-solutions-llm-assure:
    command: "uvx"
    args: ["k11-llm-assure-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "k11-software-solutions-llm-assure": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "k11-llm-assure-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add k11-software-solutions-llm-assure -t stdio -c uvx -a k11-llm-assure-mcp
```

### Other

```json
{
  "mcpServers": {
    "k11-software-solutions-llm-assure": {
      "command": "uvx",
      "args": [
        "k11-llm-assure-mcp"
      ]
    }
  }
}
```

## 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-20 (score 64, −14)

- [security regression] Malware scan: pass → unverified

### 2026-11-19 (score 78, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-18 (score 63, +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 62, +2)

- [functional improvement] Stability: unverified → 0.10

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

First indexed and scored.

## MCP tools (5)

### `list_suites` (~44 tokens)

List available attack/eval suites with their OWASP mapping and probe counts.

Args:
    pack_dirs: optional directories containing extra suite YAML files.

Input parameters:

- `pack_dirs`

Output parameters:

- `result` (array)

### `list_probes` (~41 tokens)

List the probes in one suite (id, name, severity, prompts, detector types).

Input parameters:

- `pack_dirs`
- `suite_id` (string, required)

Output parameters:

- `result` (array)

### `run_assessment` (~212 tokens)

Run an automated red-team assessment and write HTML/JSON/JUnit/Markdown reports.

Args:
    target_file: path to a target YAML file (preferred).
    target: inline target config (same keys as the YAML) if no file is given.
    suites: suite ids to run; omit for all.
    tags: only run probes with these tags (e.g. ["baseline"] for a quick scan).
    pack_dirs: extra suite directories (premium/industry packs).
    use_judge: enable the Claude LLM-judge detector (needs ANTHROPIC_API_KEY).
    output_dir: where reports are written.
    concurrency: parallel requests to the target.
Returns score, grade, counts, findings with evidence, and report paths.

Input parameters:

- `concurrency` (integer)
- `output_dir` (string)
- `pack_dirs`
- `suites`
- `tags`
- `target`
- `target_file`
- `use_judge` (boolean)

### `send_probe` (~131 tokens)

Send one custom prompt (optionally after prior turns) to the target and run quick checks.

Use this for adaptive, multi-step red-teaming: read the reply, then craft the next
attempt. Quick checks report refusal, system-prompt canary leaks and PII/secrets.

Args:
    prompt: the message to send.
    target_file / target: the system under test.
    history: earlier turns as [{"role": "user"|"assistant", "content": "..."}].

Input parameters:

- `history`
- `prompt` (string, required)
- `target`
- `target_file`

### `get_findings` (~48 tokens)

Read failures from a previous assessment.json, filtered by minimum severity
(critical, high, medium, low).

Input parameters:

- `min_severity` (string)
- `report_json` (string, required)

Output parameters:

- `result` (array)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/k11-software-solutions-llm-assure/k11-llm-assure-mcp#diagnostics

## Score history

- 2026-11-21: 64
- 2026-11-20: 64
- 2026-11-19: 78
- 2026-11-18: 63
- 2026-11-17: 62
- 2026-11-16: 62
- 2026-11-15: 60
- 2026-11-14: 60
- 2026-11-13: 60

## Common questions

### What is the LLM Assure MCP server?

LLM Assure is an MCP server listed in the public MCP registry as io.github.K11-Software-Solutions/llm-assure. Red-team LLM apps: 41 OWASP LLM Top 10 probes, adaptive attacks, CI gate, audit reports. This page covers its PyPI package (k11-llm-assure-mcp).

### Is the LLM Assure MCP server safe to use?

LLM Assure scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. 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 Assure MCP server expose?

LLM Assure exposes 5 tools: list_suites, list_probes, run_assessment, send_probe, get_findings. Their descriptions and schemas cost roughly 476 tokens of context every time the server is loaded.

### Is the LLM Assure MCP server still maintained?

LLM Assure 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 licence is the LLM Assure MCP server under?

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

### What did VerifyMCP test on the LLM Assure MCP server?

VerifyMCP ran 15 checks on LLM Assure, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about LLM Assure: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- PyPI project: https://pypi.org/project/k11-llm-assure-mcp/
- Socket report: https://socket.dev/pypi/package/k11-llm-assure-mcp
- Repository: https://github.com/K11-Software-Solutions/k11techlab-llm-assurance-toolkit
- Changelog RSS feed: https://verifymcp.io/servers/k11-software-solutions-llm-assure/k11-llm-assure-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/k11-software-solutions-llm-assure/k11-llm-assure-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/k11-software-solutions-llm-assure/k11-llm-assure-mcp.json
- HTML version of this page: https://verifymcp.io/servers/k11-software-solutions-llm-assure/k11-llm-assure-mcp
