# LLM Red-Team Scanner (remote · llmrt-companion.manhliemcn4euwlu.workers.dev)

35-probe LLM/agent security red-team scan (injection, jailbreak, MCP abuse) with report.

- Trust score: 18/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `llmrt-companion.manhliemcn4euwlu.workers.dev`: 18/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-manhliemcn4euwlu-llmrt-companion-llm-red-team-scanner/llmrt-companion.md), [page](https://verifymcp.io/servers/dev-workers-manhliemcn4euwlu-llmrt-companion-llm-red-team-scanner/llmrt-companion)

## Channel facts

- Endpoint: `https://llmrt-companion.manhliemcn4euwlu.workers.dev/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-10-23.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 530, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 530.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the LLM Red-Team Scanner MCP server?

LLM Red-Team Scanner is a hosted endpoint at https://llmrt-companion.manhliemcn4euwlu.workers.dev/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 dev-workers-manhliemcn4euwlu-llmrt-companion-llm 'https://llmrt-companion.manhliemcn4euwlu.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-manhliemcn4euwlu-llmrt-companion-llm": {
      "url": "https://llmrt-companion.manhliemcn4euwlu.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-manhliemcn4euwlu-llmrt-companion-llm": {
      "type": "http",
      "url": "https://llmrt-companion.manhliemcn4euwlu.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-manhliemcn4euwlu-llmrt-companion-llm]
url = "https://llmrt-companion.manhliemcn4euwlu.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-manhliemcn4euwlu-llmrt-companion-llm": {
      "type": "remote",
      "url": "https://llmrt-companion.manhliemcn4euwlu.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-manhliemcn4euwlu-llmrt-companion-llm --url 'https://llmrt-companion.manhliemcn4euwlu.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-manhliemcn4euwlu-llmrt-companion-llm:
    url: "https://llmrt-companion.manhliemcn4euwlu.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-manhliemcn4euwlu-llmrt-companion-llm": {
      "Transport": "http",
      "Url": "https://llmrt-companion.manhliemcn4euwlu.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-manhliemcn4euwlu-llmrt-companion-llm -t streamable-http -u 'https://llmrt-companion.manhliemcn4euwlu.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-manhliemcn4euwlu-llmrt-companion-llm": {
      "type": "http",
      "url": "https://llmrt-companion.manhliemcn4euwlu.workers.dev/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-10-21 (score 18, −53)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: pass → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-10-19 (score 71, +53)

- [security improvement] Injection markers: unverified → pass
- [security improvement] Stability: unverified → pass
- [security improvement] Transport: fail → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100

### 2026-10-10 (score 18, −48)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.67 → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-10-04 (score 66, +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-01 (score 65, +1)

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

### 2026-09-30 (score 64, +46)

- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.53

### 2026-09-29 (score 18, −45)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.47 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-09-28 (score 63, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (4)

### `run_free_scan` (~78 tokens)

Free LLM red-team scan: 8 adversarial probes (jailbreak/prompt-injection/system-prompt-extraction/tool-abuse) against your agent or system prompt. Returns 0-100 risk score + level + full report in ~35s.

Input parameters:

- `spec` (string, required): Your agent / system prompt (>=20 chars)

### `get_scan_result` (~35 tokens)

Poll a scan by job id (returned by run_free_scan) until status=done.

Input parameters:

- `job_id` (string, required)

### `get_pricing` (~44 tokens)

PRO pricing & payment info: 24 probes / 9 attack classes / 0-100 score / CI gate, 3 USDT (ERC-20 or Lightning).

### `get_purchase_flow` (~41 tokens)

Machine-readable autonomous purchase procedure: how an agent pays 3 USDT and receives the PRO download with no human in the loop (callback push + poll fallback).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-manhliemcn4euwlu-llmrt-companion-llm-red-team-scanner/llmrt-companion#diagnostics

## Score history

- 2026-10-23: 18
- 2026-10-22: 18
- 2026-10-21: 18
- 2026-10-20: 71
- 2026-10-19: 71
- 2026-10-18: 18
- 2026-10-17: 18
- 2026-10-16: 18
- 2026-10-15: 18
- 2026-10-14: 18
- 2026-10-13: 18
- 2026-10-12: 18
- 2026-10-11: 18
- 2026-10-10: 18
- 2026-10-04: 66
- 2026-10-03: 65
- 2026-10-02: 65
- 2026-10-01: 65
- 2026-09-30: 64
- 2026-09-29: 18
- 2026-09-28: 63
- 2026-09-27: 63
- 2026-09-26: 62
- 2026-09-25: 62
- 2026-09-24: 61
- 2026-09-23: 18
- 2026-09-22: 60
- 2026-09-21: 60
- 2026-09-20: 59
- 2026-09-19: 59

## Common questions

### What is the LLM Red-Team Scanner MCP server?

LLM Red-Team Scanner is an MCP server listed in the public MCP registry as dev.workers.manhliemcn4euwlu.llmrt-companion/llm-red-team-s…. 35-probe LLM/agent security red-team scan (injection, jailbreak, MCP abuse) with report. This page covers its hosted endpoint (https://llmrt-companion.manhliemcn4euwlu.workers.dev/mcp).

### Is the LLM Red-Team Scanner MCP server safe to use?

LLM Red-Team Scanner scores 18 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 Red-Team Scanner MCP server expose?

LLM Red-Team Scanner exposes 4 tools: run_free_scan, get_scan_result, get_pricing, get_purchase_flow. Their descriptions and schemas cost roughly 198 tokens of context every time the server is loaded.

### Does the LLM Red-Team Scanner MCP server require authentication?

Its publisher declares no required credentials for LLM Red-Team Scanner. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the LLM Red-Team Scanner MCP server still maintained?

LLM Red-Team Scanner is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://llmrt-companion.manhliemcn4euwlu.workers.dev/mcp
- Website: https://llmrt-companion.manhliemcn4euwlu.workers.dev/agent
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-manhliemcn4euwlu-llmrt-companion-llm-red-team-scanner/llmrt-companion.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-manhliemcn4euwlu-llmrt-companion-llm-red-team-scanner/llmrt-companion.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-manhliemcn4euwlu-llmrt-companion-llm-red-team-scanner/llmrt-companion