
Mcp Audit Server
Run AI agent and MCP security audits from your coding agent via a thin stdio proxy to a hosted or self-hosted audit backend before you trust new tools in production.
Overview
mcp-audit-server is a MCP server for the Ship phase that proxies your agent to a hosted backend for AI agent and MCP security auditing.
What is this MCP server?
- Thin MCP and CLI proxy to a hosted AI agent and MCP security auditing backend
- npm ledd-mcp-audit-server v2.1.0 with stdio transport for agent-driven scans
- Requires AGENT_SECURITY_API_KEY for the managed hosted audit service
- Optional AGENT_SECURITY_BASE_URL for self-hosted or private HTTPS API origins
- Keeps audit logic remote—local install is only the MCP/CLI façade
- Registry version 2.1.0
- npm identifier ledd-mcp-audit-server with stdio transport
- Two primary configuration env vars (API key required, base URL optional)
What problem does it solve?
You are enabling multiple MCP servers and agent tools but lack a repeatable way to security-audit those configurations from inside your development agent.
Who is it for?
Solo builders hardening Claude Code or Cursor setups who want managed or self-hosted audit APIs wired through stdio MCP.
Skip if: Teams that only need generic SAST on application source and do not run MCP or autonomous agent surfaces.
What do I get? / Deliverables
You can trigger agent and MCP security audits through MCP tool calls using an API key—and optional private base URL—before promoting tools to production users.
- MCP-invokable security audit runs against agents and MCP setups
- CLI-capable same proxy for terminal-driven audits
- Configurable API origin for managed vs private audit deployments
Recommended MCP Servers
Journey fit
How it compares
Security-audit MCP proxy to a hosted backend—not a full on-prem scanner appliance or a coding skill.
Common Questions / FAQ
Who is mcp-audit-server for?
It is for developers and indie operators who deploy MCP-enabled agents and need a thin local MCP/CLI client that talks to Ledd’s agent and MCP security audit API.
When should I use mcp-audit-server?
Use it in Ship during security review—when adding new MCP servers, changing agent permissions, or before launch—so audits run from the same environment you configure tools.
How do I add mcp-audit-server to my agent?
Install ledd-mcp-audit-server from npm, set AGENT_SECURITY_API_KEY, optionally AGENT_SECURITY_BASE_URL for self-hosted APIs, add the stdio server to your MCP client, and invoke audit tools from your agent.