Remote MCP · Endpoint

LLM Security Scanner: Red-Team, Jailbreak, Prompt Injection Audit MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://llmrt-companion.manhliemcn4euwlu.workers.dev/mcp

The last check failed: the server returned an HTTP error.

Registry name
dev.workers.manhliemcn4euwlu.llmrt-companion/llm-red-team-scanner
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
5 tools
Uptime, last 30 days
44.4% from 18 checks
Described by its publisher as
35-probe LLM/agent security red-team scan (injection, jailbreak, MCP abuse) with report.
Website
https://llmrt-companion.manhliemcn4euwlu.workers.dev/agent
Listing
From the official MCP registry (active).
Recent checks of LLM Security Scanner: Red-Team, Jailbreak, Prompt Injection Audit
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
1 day agoHandshake completed693 ms
2 days agoHandshake completed406 ms
3 days agoHandshake completed658 ms
4 days agoHandshake completed8.87 s
5 days agoHandshake completed1.91 s
6 days agoFailed - the server returned an HTTP error—
9 days agoFailed - the server returned an HTTP error—
12 days agoFailed - the server returned an HTTP error—
14 days agoFailed - the server returned an HTTP error—
16 days agoHandshake completed416 ms
18 days agoHandshake completed1.94 s
20 days agoFailed - the server returned an HTTP error—
22 days agoFailed - the server returned an HTTP error—
24 days agoFailed - the server returned an HTTP error—
26 days agoFailed - the server returned an HTTP error—
27 days agoHandshake completed667 ms
28 days agoFailed - the server returned an HTTP error—

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 29.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with LLM Security Scanner: Red-Team, Jailbreak, Prompt Injection Audit and makes no claim about it beyond what these checks measured.