Remote MCP · Endpoint

Prompt Injection Scanner MCP server

No. Prompt Injection Scanner answered an MCP handshake 19 minutes ago.

UpLast checked 19 minutes ago

Server URL

https://injectionscan.openkrill.app/mcp

The last check completed an MCP handshake.

Registry name
app.openkrill/injection-scan
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
353 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Check text before your agent reads it: hidden instructions, invisible text and links that leak data.
Listing
From the official MCP registry (active).
Recent checks of Prompt Injection Scanner
CheckedResultHandshake
19 minutes agoHandshake completed353 ms
10 days agoHandshake completed395 ms
10 days agoHandshake completed590 ms
11 days agoHandshake completed314 ms
13 days agoHandshake completed290 ms
14 days agoHandshake completed157 ms
14 days agoHandshake completed725 ms
15 days agoHandshake completed146 ms
17 days agoHandshake completed336 ms
19 days agoHandshake completed150 ms
21 days agoHandshake completed123 ms
24 days agoHandshake completed142 ms
26 days agoHandshake completed370 ms
28 days agoHandshake completed357 ms

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

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.

Listing data comes from the official MCP registry. Glide is not affiliated with Prompt Injection Scanner and makes no claim about it beyond what these checks measured.