Server detail
Auditra exposes a focused MCP interface for auditing WordPress plugins directly from your IDE or AI assistant. Instead of manually scanning codebases or running disparate CLI tools, you get a standardized `audit_plugin` method that accepts a plugin slug or local path and returns structured findings: outdated dependencies, known CVEs, coding-standard violations, deprecated API usage, and permission overreach. The server wraps WP-CLI, PHP_CodeSniffer (WordPress ruleset), Composer audit, and a curated vulnerability database, so results are consistent and actionable. Typical workflows include pre-merge checks in CI, quick vetting of third-party plugins before installation, and automated reporting for client site maintenance. Integration is zero-config for most stacks — add the server to your MCP client (Cursor, Claude Desktop, Continue, etc.) and call the tool like any other function. Compared to standalone SAST scanners, Auditra is WordPress-aware: it understands plugin architecture, hook semantics, and the WP.org update cycle, reducing false positives. It doesn't replace deep static analysis but excels at the 80% of issues that are WP-specific and immediately remediable. Open-source (MIT), community-maintained, and extensible via custom rule packs.
An MCP server that exposes Auditra capabilities to MCP-compatible AI clients.
Collections featuring this MCP
Tool testing
auditra
Call the MCP capabilities provided by Auditra and return a structured result.
inputPass arguments according to the server tool schema.Connection modes
{
"mcpServers": {
"Auditra": {
"url": "Generated by the provider after deployment"
}
}
}The Remote endpoint is generated by the provider after deployment; this page does not fabricate an unusable endpoint.
No npm package is recorded. Open the source repository to complete command and args.If no npm package is registered, follow the installation method in the source repository.
How to use
- 01Step 1
Review server capabilities and permission scope.
- 02Step 2
Copy the install command or JSON configuration.
- 03Step 3
Run a small connection test in your client.
- 04Step 4
Adopt it long term only after reviewing access and maintenance.
Discussions
Use this space to keep checking source information, usage experience and maintenance status.
Open source page