Remote MCP · Endpoint

LLM Red-Team Scanner 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
4 tools
Uptime, last 30 days
58.8% from 17 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 Red-Team Scanner
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
7 days agoHandshake completed667 ms
8 days agoFailed - the server returned an HTTP error—
9 days agoFailed - the server returned an HTTP error—
12 days agoHandshake completed775 ms
13 days agoHandshake completed607 ms
15 days agoHandshake completed657 ms
16 days agoHandshake completed613 ms
18 days agoHandshake completed777 ms
19 days agoHandshake completed700 ms
20 days agoHandshake completed573 ms
20 days agoHandshake completed988 ms
21 days agoHandshake completed480 ms
22 days agoFailed - the server returned an HTTP error—

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

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 Red-Team Scanner and makes no claim about it beyond what these checks measured.