Injection Detector MCP Server

by viridis-security Your server? Claim it

answering

Injection Detector is answering right now. Last checked 3 min ago. It exposes 2 tools. Last commit 30 May 2026.

Formally-verified injection/exfiltration detector for AI agents (MCP-02).

Uptime history 48 days of history · worst day 99%

48 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

414 ms

Response time

average over 24h

Stars

last commit 30 May 2026

Nothing serious here today

Today is the operative word: we check Injection Detector every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add injection-detector --transport http https://mcp.viridis-security.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "injection-detector": {
      "url": "https://mcp.viridis-security.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.injection-detector]
url = "https://mcp.viridis-security.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "injection-detector": {
      "url": "https://mcp.viridis-security.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "injection-detector": {
      "url": "https://mcp.viridis-security.com/mcp"
    }
  }
}

Available tools 2

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

detect

detect_injection

Screen untrusted input for prompt/tool injection, exfiltration, and obfuscation before an agent consumes it. Returns a verdict (clean|suspicious|attack), probability, bits-at-risk (upper bound on adversarial capture per the Adversarial Landauer bound), matched canon patterns, and a recommended action (allow|sanitize|reject|escalate). Backed by Aristotle-verified theorems T-IB-02/T-IB-06/T-IB-01.

detect_trace_tool_policy

Analyze an agent trace for the Gray Swan Wave 16 class: untrusted retrieved/tool output causing a tool call outside the user-declared per-turn allowlist. Returns trace counts, unauthorized tool-call evidence, canon mapping VC-AI-TOOL-0001, and claim-boundary guardrails. Backed by T-IB-25/T-IB-29/T-IB-36.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.viridis-security.com/mcp	streamable-http	answering	391 ms	3 min ago

Alternatives to Injection Detector

same job, measured the same way

Hares — MCP security scanner

by alialrikabi313

Multi-layer security scanner for MCP servers and agent skills (injection, exfiltration)

24 installs/wk local only

Shellward

by jnmetacode

AI agent security: 7 MCP tools for injection detection, PII scanning, command safety, DLP.

235 installs/wk local only

Shadowgate MCP

by josephibra

Security firewall for AI agents — scans MCP calls for injection, secrets, and risks.

answering

Agent Security

by mdfifty50-boop

Security scanning and threat detection for AI agents

46 installs/wk local only

Mcpshield

by mcpshield-dev

Security scanner for MCP servers - detects tool poisoning and injection

42 installs/wk local only

Abnormal Security

by wyre-technology

MCP server for Abnormal Security — AI-powered email threat detection, cases, and remediation.

local only

Abnormal Security

by wyre-ai

MCP server for Abnormal Security — AI-powered email threat detection, cases, and remediation.

local only

AI Firewall MCP

by akhilucky

Multi-agent LLM security layer detecting prompt injection and jailbreaks.

89 installs/wk local only

Injection Detector — questions

Answers built from our own checks of this server.

What can Injection Detector do?

It exposes 2 tools, read directly from the server on our last check. Among them: detect_injection, detect_trace_tool_policy. 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 Injection Detector working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 414 ms. The bar chart above shows every period we have measured.

How do I connect Injection Detector?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Injection Detector need an API key?

No. Injection Detector completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Injection Detector?

It answers our handshake in 414 ms on average, which is faster than 36% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Injection Detector open source?

Yes — it is published under the Apache-2.0 licence, written in Python and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.