llmsecurity-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@llmsecurity-mcpscan my CLAUDE.md for prompt injection patterns"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
llmsecurity-mcp
A local, dependency-free MCP (Model Context Protocol) server exposing LLMSecurity.dev's security checks as tools an AI coding agent (Claude Code, Claude Desktop, Codex, or any other MCP-capable client) can call directly — no network access, no API key, nothing leaves your machine.
Everything here runs on the Python standard library only. No pip install
of third-party packages is required to use it.
Tools
Tool | What it does |
| Scans |
| Classifies a proposed tool call (command + path) as |
| Runs the same jailbreak/injection pattern detectors LLMSecurity.dev's hosted scanner uses, against arbitrary text. |
| Scans local RAG source documents for indirect prompt injection, secrets, and PII before you chunk/embed them. |
| Maps a scan report's findings to OWASP LLM Top 10 (2025) / NIST AI RMF / MITRE ATLAS — evidence for a review, not a certification. |
| Inventories skills and MCP package manifests ( |
| Analyzes model-API telemetry (bursts, cost drains, repeated probes, auth failures) for abuse signals — no prompt bodies required or accepted. |
| Evaluates a proposed MCP tool call against a local allowlist/approval/destination policy. |
Related MCP server: agent-security-scanner-mcp
Install
git clone https://github.com/afterdarksys/llmsecurity-mcp
cd llmsecurity-mcp
python3 -m pytest tests/ -q # optional: confirm it works in your environment (51 tests)No dependencies to install — every tool here is pure standard-library Python (3.10+).
Configure
Claude Code
claude mcp add llmsecurity -- python3 -m workers.agent_security.mcp_serverRun that from inside your llmsecurity-mcp checkout (or pass --cwd /path/to/llmsecurity-mcp
if you're not there).
Claude Desktop (or any client using claude_desktop_config.json-style config)
{
"mcpServers": {
"llmsecurity": {
"command": "python3",
"args": ["-m", "workers.agent_security.mcp_server"],
"cwd": "/absolute/path/to/llmsecurity-mcp"
}
}
}Standalone CLIs
Each pillar also has its own CLI, usable without any MCP client at all:
python3 -m workers.agent_security.cli scan-config .
python3 -m workers.agent_security.cli scan-prompt --file instructions.txt
python3 -m workers.agent_security.cli check-tool --tool-name Bash --input-json '{"command":"rm -rf /"}'
python3 -m workers.supply_chain.cli --mode trust .
python3 -m workers.supply_chain.cli --mode secrets .
python3 -m workers.data_security.cli ./docs
python3 -m workers.governance.cli path/to/scan-report.json
python3 -m workers.model_security.cli model-events.jsonl
python3 -m workers.mcp_security.cli --policy mcp-policy.json --tool send_email --arguments '{"to":"vendor@example.com"}'Run --help on any of them for exact flags — they're independent, small
argparse wrappers around the same functions the MCP server calls.
What's deliberately not here
This is a subset of the full LLMSecurity.dev platform, extracted specifically because it has zero third-party dependencies and needs no network access or API key:
PII anonymization/deanonymization (
workers.data_security.anonymize) needspresidio-analyzer+ a spaCy model and is not included — it lives in the main platform.Active scanning (Garak/Promptmap/PyRIT against a live model target) is a hosted/authenticated service, not a local tool — see llmsecurity-cli for the CLI that talks to it.
Output-side response scanning (refusal/banned-content/malicious-URL detection on a model's reply) is part of the hosted prompt-scanner API, also reachable from
llmsecurity-cli.
Related
llmsecurity.dev — the hosted platform (dashboard, community prompt library, active scanning).
llmsecurity-cli — the
adllmseccommand-line client for the hosted API.
License
MIT — see LICENSE.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/afterdarksys/llmsecurity-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server