mcpbeat Sign in

LLM Red-Team Scanner MCP Server

by workers-manhliemcn4euwlu-llmrt-companion Your server? Claim it
answering

LLM Red-Team Scanner is answering right now. Last checked 9 min ago. It exposes 5 tools.

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

Uptime history 49 days of history · worst day 0%
49 days agonow
96.7%
Uptime 24h
88 of 91 checks
5
Tools
read from the server
675 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 5

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 19 September 2026. No other catalogue keeps this.

30 Oct 3 tool descriptions were rewritten get_pricing, get_purchase_flow, run_free_scan
30 Oct a tool appeared validate
18 Sep a tool description was rewritten get_pricing

LLM Red-Team Scanner does not always answer

Over the last week it answered 51.6% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add llm-red-team-scanner --transport http https://llmrt-companion.manhliemcn4euwlu.workers.dev/mcp
Settings → Connectors → Add custom connector, then paste this address
https://llmrt-companion.manhliemcn4euwlu.workers.dev/mcp
~/.codex/config.toml
[mcp_servers.llm-red-team-scanner]
url = "https://llmrt-companion.manhliemcn4euwlu.workers.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "llm-red-team-scanner": {
      "url": "https://llmrt-companion.manhliemcn4euwlu.workers.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "llm-red-team-scanner": {
      "type": "http",
      "url": "https://llmrt-companion.manhliemcn4euwlu.workers.dev/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

free
run_free_scan
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.
pricing
get_pricing
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.
purchase
get_purchase_flow
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).
scan
get_scan_result
Poll a scan by job id (returned by run_free_scan) until status=done.
validate
validate
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.

Endpoints

URLTransportStateLatencyChecked
https://llmrt-companion.manhliemcn4euwlu.workers.dev/mcp streamable-http answering 491 ms 9 min ago

Alternatives to LLM Red-Team Scanner

same job, measured the same way
Sentrint
by sentrint

Code security scanner for founders and small teams: leaked secrets, missing RLS, injection, CVEs

answering
MCP Gateway Scan
by willianpinho

Read-only MCP/agent-gateway readiness scanner — scores a repo across 7 security dimensions.

52 installs/wk local only
SafePrompt
by safeprompt

Detect prompt injection, jailbreaks, and code injection in untrusted text before it reaches an LLM.

254 installs/wk 2 tools answering
GuardianShield
by sparkvibe-io

AI security layer: code scanning, PII detection, prompt injection, secrets, CVEs

84 installs/wk local only
MCP Code Review Server
by goodjobwilliam

Code review as an MCP server — structured reviews with OWASP security scanning.

64 installs/wk local only
Abnormal Security MCP
by servosity

Abnormal Security email threats, cases, and reporting in your terminal and your AI agents.

local only
SecurityScan
by apisecurityscan

Scan GitHub-hosted AI skills for vulnerabilities: prompt injection, malware, OWASP LLM Top 10.

8 tools answering
SecScan
by secscan

Scan, monitor and fix a live web app from your editor: graded security reports with fix prompts.

12 tools answering

LLM Red-Team Scanner — questions

Answers built from our own checks of this server.

What can LLM Red-Team Scanner do?
It exposes 5 tools, read directly from the server on our last check. Among them: get_pricing, get_purchase_flow, get_scan_result, run_free_scan, validate. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is LLM Red-Team Scanner working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 88 of 91 checks got a reply (96.7%), average response time 675 ms. The bar chart above shows every period we have measured.
How do I connect LLM Red-Team Scanner?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does LLM Red-Team Scanner need an API key?
No. LLM Red-Team Scanner completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is LLM Red-Team Scanner?
It answers our handshake in 675 ms on average, which is faster than 15% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.