mcpbeat Sign in

Injection Detector MCP Server

by viridis-security Your server? Claim it
answering

Injection Detector is answering right now. Last checked 5 min ago. It exposes 2 tools. Last commit 1 Nov 2026.

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

Uptime history 91 days of history · worst day 99%
91 days agonow
100.0%
Uptime 24h
92 of 92 checks
2
Tools
read from the server
418 ms
Response time
average over 24h
1
Stars
last commit 1 Nov 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.

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 5 min ago.

run in your terminal
claude mcp add injection-detector --transport http https://mcp.viridis-security.com/mcp
Settings → Connectors → Add custom connector, then paste this address
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
{
  "servers": {
    "injection-detector": {
      "type": "http",
      "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

URLTransportStateLatencyChecked
https://mcp.viridis-security.com/mcp streamable-http answering 562 ms 5 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)

60 installs/wk local only
Shellward
by jnmetacode

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

332 installs/wk local only
Shadowgate MCP
by josephibra

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

answering
A
AI Agent Security Scanner
by workers-manhliemcn4euwlu-llmrt-companion

Security scanner for AI agents and MCP servers: injection, jailbreak, tool abuse.

5 tools answering
Agent Security
by mdfifty50-boop

Security scanning and threat detection for AI agents

79 installs/wk local only
P
Prembly MCP Server
by prembly

Identity verification, compliance and fraud detection checks from Prembly, for LLM clients.

answering
Mcpshield
by mcpshield-dev

Security scanner for MCP servers - detects tool poisoning and injection

47 installs/wk local only
Agent Skill & Config Security Audit
by tylerscomic-lab

Scan AI agent skills and configs for hidden Unicode, prompt injection and exfiltration.

answering

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 418 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 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 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 418 ms on average, which is faster than 32% 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?
The code is open source: it is published under the Apache-2.0 licence, written in Python, 1 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at mcp.viridis-security.com, which runs on its operator's own terms.