mcp-audit-server
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., "@mcp-audit-serveraudit my claude_desktop_config.json for security issues"
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.
mcp-audit-server
Thin MCP server and CLI proxy for AI agent and MCP security auditing. It connects to a private audit API to analyze MCP configurations, test prompt injection resistance, trace data flows, scan packages, and generate security policies.
This package is a thin proxy. All scan logic lives in a private backend operated by you or your provider.
Managed hosted flow:
set
AGENT_SECURITY_API_KEYthe package will automatically target
https://audit.leddconsulting.com
Self-hosted or private-network flow:
set
AGENT_SECURITY_BASE_URLto your HTTPS API originor set
AGENT_SECURITY_HOSTandAGENT_SECURITY_PORTfor a loopback/private deployment
Hosted backend access is not bundled with this package. If you want managed access or a licensed private deployment, contact Ledd Consulting.
Registry and Directories
npm package:
ledd-mcp-audit-serverOfficial MCP Registry name:
io.github.joepangallo/mcp-audit-serverDownstream directories such as Glama and PulseMCP should ingest from the official MCP Registry, so you usually do not need separate manual submissions for each site.
Glama authorship claim is optional. It only gives you ownership of the Glama page and access to manual sync and re-scan controls.
Related MCP server: github-security-mcp
Install
npm install ledd-mcp-audit-serverInstall package: ledd-mcp-audit-server
CLI command after install: mcp-audit-server
This is the public package that should be published to npm and listed in public MCP directories. The audit engine itself stays private.
The old package name mcp-server-agent-security is retired. See MIGRATION.md for upgrade steps and the deprecation plan.
Usage as MCP Server
Add to your MCP client configuration (Claude Desktop, Cursor, etc.):
{
"mcpServers": {
"mcp-audit-server": {
"command": "npx",
"args": ["-y", "ledd-mcp-audit-server", "--mcp"],
"env": {
"AGENT_SECURITY_API_KEY": "your-issued-api-key"
}
}
}
}For a self-hosted backend, add AGENT_SECURITY_BASE_URL to that same env block.
The server exposes 10 tools over stdio:
Tool | Description |
| Static analysis of MCP config JSON for privilege, auth, transport, and launch risks |
| Active probing of a running MCP server over stdio (requires |
| Trust audit for tool permissions, execution provenance, secret exposure controls, policy drift, and deployment trust score |
| Tests a system prompt against a 30+ payload injection catalog |
| Traces PII and secret exposure through an agent's tool pipeline |
| Scans an npm MCP package for dependency vulnerabilities and dangerous patterns |
| Combines multiple audit results into a composite report with executive summary |
| Auto-remediates config issues: removes unsafe flags, upgrades transport, redacts secrets |
| Appends injection-resistant guardrails to a system prompt |
| Generates an enforceable JSON security policy from an MCP config |
Usage as CLI
The CLI forwards commands to the private audit API.
# Hosted quick start
export AGENT_SECURITY_API_KEY=your-issued-api-key
# Audit an MCP configuration file
mcp-audit-server scan-config ./claude_desktop_config.json
# Probe a live MCP server (requires AGENT_SECURITY_ADMIN_MODE=1)
mcp-audit-server scan-server npx -y @modelcontextprotocol/server-filesystem /tmp
# Audit trust posture and policy drift for an agent/MCP deployment
mcp-audit-server scan-trust ./claude_desktop_config.json ./claimed-policy.json
# Scan an npm package for vulnerabilities
mcp-audit-server scan-package @modelcontextprotocol/server-shell
# Test a system prompt for injection vulnerabilities
mcp-audit-server scan-injection ./system-prompt.txt
# Trace data flows through an MCP config
mcp-audit-server scan-dataflow ./claude_desktop_config.json
# Auto-fix security issues in an MCP config
mcp-audit-server fix-config ./claude_desktop_config.json
# Harden a system prompt against injection
mcp-audit-server harden-prompt ./system-prompt.txt
# Generate a security policy from an MCP config
mcp-audit-server generate-policy ./claude_desktop_config.json
# Retrieve a previous audit report
mcp-audit-server report <audit-id>
# Output raw JSON instead of formatted tables
mcp-audit-server scan-config ./config.json --json
# Start in MCP stdio server mode
mcp-audit-server --mcpFor a self-hosted backend, also set AGENT_SECURITY_BASE_URL=https://your-audit-host.
Environment Variables
Variable | Default | Description |
| (none) | Full audit API origin, e.g. |
|
| Self-hosted/private-network audit API host |
|
| Self-hosted/private-network audit API port |
| (none) | API key for authenticated access. If set with no endpoint overrides, the package uses |
|
| Request timeout for CLI and MCP proxy calls |
| (none) | Set to |
What It Detects
Tool spoofing -- duplicate tool names, namespace collision (CWE-290)
Rug pull -- unpinned packages, version drift (CWE-829)
Prompt injection -- direct override, instruction hijacking, role-play escape, delimiter injection, encoding bypass, multilingual injection
Privilege escalation -- overprivileged tools, shell execution without allowlists, unrestricted filesystem access
Data exfiltration -- PII leakage through tool pipelines, outbound network paths
Insecure transport -- missing TLS, plaintext credentials in config
Missing auth -- unauthenticated MCP servers, missing API key requirements
Shell injection -- arbitrary command execution via tool configurations
Path traversal -- unrestricted filesystem scope in tool arguments
SQL injection -- raw SQL patterns in tool definitions
Rate limiting -- missing request throttling on exposed tools
Package vulnerabilities -- known CVEs in npm MCP package dependencies
Credential exposure -- inline secrets, missing rotation policies
Agent trust drift -- claimed-safe policies that do not match configured tools, network posture, or observed action logs
Weak provenance -- missing action/evidence capture for risky agent operations
Requirements
Node.js >= 18
Access to a private audit API. The managed hosted default is
https://audit.leddconsulting.comwhenAGENT_SECURITY_API_KEYis set. UseAGENT_SECURITY_BASE_URLfor other hosted HTTPS deployments, orAGENT_SECURITY_HOSTandAGENT_SECURITY_PORTfor local/private-network deployments.
License
MIT
Built by Ledd Consulting
This server cannot be installed
Maintenance
Latest Blog Posts
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/joepangallo/mcp-audit-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server