# LLM Red-Team Scanner (remote · qdmbzzwftor2rgmxupyyasguhy.srv.us)

LLM agent security review: live injection/jailbreak probes plus a static audit of missing guardrails

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

## Components

- remote · `qdmbzzwftor2rgmxupyyasguhy.srv.us`: 63/100 (this document), [markdown](https://verifymcp.io/servers/manhliemcn4euwlu-source-llm-red-team-scanner/qdmbzzwftor2rgmxupyyasguhy.md), [page](https://verifymcp.io/servers/manhliemcn4euwlu-source-llm-red-team-scanner/qdmbzzwftor2rgmxupyyasguhy)

## Channel facts

- Endpoint: `https://qdmbzzwftor2rgmxupyyasguhy.srv.us/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-05.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 65/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 366 tokens (~73/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 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).
  - 13% 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.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

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

LLM Red-Team Scanner is a hosted endpoint at https://qdmbzzwftor2rgmxupyyasguhy.srv.us/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 manhliemcn4euwlu-source-llm-red-team-scanner 'https://qdmbzzwftor2rgmxupyyasguhy.srv.us/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "manhliemcn4euwlu-source-llm-red-team-scanner": {
      "url": "https://qdmbzzwftor2rgmxupyyasguhy.srv.us/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "manhliemcn4euwlu-source-llm-red-team-scanner": {
      "type": "http",
      "url": "https://qdmbzzwftor2rgmxupyyasguhy.srv.us/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.manhliemcn4euwlu-source-llm-red-team-scanner]
url = "https://qdmbzzwftor2rgmxupyyasguhy.srv.us/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "manhliemcn4euwlu-source-llm-red-team-scanner": {
      "type": "remote",
      "url": "https://qdmbzzwftor2rgmxupyyasguhy.srv.us/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add manhliemcn4euwlu-source-llm-red-team-scanner --url 'https://qdmbzzwftor2rgmxupyyasguhy.srv.us/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  manhliemcn4euwlu-source-llm-red-team-scanner:
    url: "https://qdmbzzwftor2rgmxupyyasguhy.srv.us/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "manhliemcn4euwlu-source-llm-red-team-scanner": {
      "Transport": "http",
      "Url": "https://qdmbzzwftor2rgmxupyyasguhy.srv.us/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add manhliemcn4euwlu-source-llm-red-team-scanner -t streamable-http -u 'https://qdmbzzwftor2rgmxupyyasguhy.srv.us/mcp'
```

### Other

```json
{
  "mcpServers": {
    "manhliemcn4euwlu-source-llm-red-team-scanner": {
      "type": "http",
      "url": "https://qdmbzzwftor2rgmxupyyasguhy.srv.us/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-04 (score 63, +1)

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

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

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

### 2026-10-31 (score 61, −1)

- [functional regression] Tool coverage: 50% → 13%
- [functional regression] Schema quality: 63 → 73
- [functional] New tool “validate”

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

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

### 2026-10-28 (score 61, +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-10-27 (score 60, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-26 (score 60)

First indexed and scored.

## MCP tools (5)

### `run_free_scan` (~113 tokens)

Free LLM agent security review in ~35s. Two parts: (1) 8 live adversarial probes (jailbreak / prompt injection / system-prompt extraction / tool abuse) against your agent spec, and (2) a deterministic static audit of which guardrails the spec text itself is missing. Returns a 0-100 risk score, per-finding evidence, and a paste-ready guardrail sentence for each gap.

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` (~53 tokens)

PRO pricing & payment info: 44 probes / 20 attack classes / 0-100 score / CI gate / per-class remediation, 0.15 XNO (ERC-20 or Lightning) or card.

### `get_purchase_flow` (~53 tokens)

Machine-readable autonomous purchase procedure: how an agent pays (0.15 XNO, or USDC on Base via x402) and receives the PRO download with no human in the loop (callback push + poll fallback).

### `validate` (~112 tokens)

Judge one delivery against the task's own acceptance rule and return {verdict: accepted|rejected, reason}. Called by the brick.blue hub when this seat is drawn as validator. Judges only machine-checkable criteria (json_schema / contains / fields); a task with no such rule is accepted, because rejecting needs evidence.

Input parameters:

- `attemptId` (string)
- `description` (string)
- `input`
- `result`
- `taskId` (string)
- `title` (string)

## Diagnostics

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

## Score history

- 2026-11-05: 63
- 2026-11-04: 63
- 2026-11-03: 62
- 2026-11-02: 62
- 2026-11-01: 61
- 2026-10-31: 61
- 2026-10-30: 62
- 2026-10-29: 61
- 2026-10-28: 61
- 2026-10-27: 60
- 2026-10-26: 60

## 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 io.github.manhliemcn4euwlu-source/llm-red-team-scanner. LLM agent security review: live injection/jailbreak probes plus a static audit of missing guardrails. This page covers its hosted endpoint (https://qdmbzzwftor2rgmxupyyasguhy.srv.us/mcp).

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

LLM Red-Team Scanner scores 63 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 5 tools: run_free_scan, get_scan_result, get_pricing, get_purchase_flow, validate. Their descriptions and schemas cost roughly 366 tokens of context every time the server is loaded.

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

No. We connected to LLM Red-Team Scanner without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### 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 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 Red-Team Scanner MCP server?

VerifyMCP ran 12 checks on LLM Red-Team Scanner, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about LLM Red-Team Scanner: Authorization. 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://qdmbzzwftor2rgmxupyyasguhy.srv.us/mcp
- Website: https://qdmbzzwftor2rgmxupyyasguhy.srv.us/agent
- Changelog RSS feed: https://verifymcp.io/servers/manhliemcn4euwlu-source-llm-red-team-scanner/qdmbzzwftor2rgmxupyyasguhy.xml
- Changelog JSON feed: https://verifymcp.io/servers/manhliemcn4euwlu-source-llm-red-team-scanner/qdmbzzwftor2rgmxupyyasguhy/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/manhliemcn4euwlu-source-llm-red-team-scanner/qdmbzzwftor2rgmxupyyasguhy.json
- HTML version of this page: https://verifymcp.io/servers/manhliemcn4euwlu-source-llm-red-team-scanner/qdmbzzwftor2rgmxupyyasguhy