Auditra MCP server
Commit Oct 6, 2026Allows AI clients to inspect and reason about a WordPress site's plugin estate, vulnerabilities, bloat, and orphaned database tables.
Also known as mwstech/auditra
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.0.2
- Last commit
- Oct 6, 2026
- License
- GPL-2.0
What is Auditra MCP?
Auditra allows AI clients to inspect and reason about a WordPress site's plugin estate, vulnerabilities, bloat, and orphaned database tables.
Summary generated from the project's README
About Auditra MCP server
Auditra transforms a WordPress installation into a read-only MCP server, allowing AI clients like Claude to inspect site data through a single REST route. By installing the plugin and generating a connection token, developers can connect an AI client via a custom connector URL. The server operates over HTTPS and uses JSON-RPC 2.0 to communicate, supporting multiple protocol revisions to ensure compatibility with different client versions.
The system uses collectors to read site context, autoloaded options, cron jobs, and database tables. It features a three-tier attribution engine that maps database elements back to specific plugins with varying confidence levels. To provide deeper insights, the server enriches data using wordpress.org and WPVulnerability services. It provides nine specific tools to help an AI agent reason about the plugin estate, bloat, and orphaned data without providing subjective verdicts or scoring.
What you can do with it
- 1Identify security risksAsk the AI client to find which plugins on the WordPress site have known vulnerabilities.
- 2Detect database bloatRequest an analysis of the options table to find elements causing performance issues.
- 3Find orphaned dataInvestigate whether deleted plugins have left behind unused database tables or options.
- 4Audit plugin ownershipUse the attribution engine to map specific database prefixes and hooks back to their owning plugins.
Written from the project's README. Every use case is checked against a quote from it.
How to install Auditra MCP
Auditra gives each account its own endpoint, so there is no address to copy here. Get yours from the provider, put it in place of the part in braces, and add it to your client as a remote server.
https://{site_domain}/wp-json/auditra/v1/mcp/%7Btoken%7D
Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablemwstech/auditra is public and reachablegithub.com/mwstech/auditra ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)GPL-2.0spdx.org/licenses/GPL-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-06github.com/mwstech/auditra ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeEndpoint did not answer initialize: unreachableFinding
README
View on GitHubAuditra
A WordPress plugin that turns the site it is installed on into a read-only MCP server, so any MCP-capable AI client (Claude custom connectors, and others) can inspect and reason about that site's plugin estate in plain language.
Ask "which of my plugins are vulnerable?", "what's bloating my options table?", or "what did deleted plugins leave behind?" — and get answers grounded in the actual state of the site.
How it works
Three layers inside one plugin, one REST route, no runtime dependencies:
- Transport —
POST /wp-json/auditra/v1/mcp/{token}speaking MCP over JSON-RPC 2.0 (plain JSON responses, stateless). Both protocol generations are served, decided per request: revision2026-07-28(per-request metadata,server/discover,Mcp-*header validation) and theinitialize-handshake revisions2025-11-25/2025-06-18/2025-03-26. Token-in-path auth behind a swappable interface, Origin validation, rate limiting, failed-auth logging. - Collectors — read WordPress directly: inventory, site context, autoloaded options, cron, database tables, content-feature usage, and a three-tier attribution engine that maps options/tables/hooks back to owning plugins with explicit confidence levels (
high= curated,medium= derived, or visibly unattributed). - Enrichment — two external services, wordpress.org and WPVulnerability, both keyless, both cached, both degrading silently with per-source coverage reporting and progressive backoff (15 min → 24 h) on failures. Support lifecycle dates for PHP, MySQL and MariaDB are not fetched at all: they ship in
includes/data/lifecycle.json, compiled from each vendor's published policy.
Nine tools; every response carries _meta (totals, truncation, sources unavailable, timestamps) and stays within a 20 KB budget. The server reports facts, never verdicts — scoring and advice are deliberately absent, because that's the AI client's job. The full design record lives in docs/DECISIONS.md.
Connect it to an AI client
- Tools → Auditra in wp-admin: enable the endpoint, generate a token, copy the connection URL.
- In Claude: Settings → Connectors → Add custom connector, paste the URL (must be
https://). - Ask questions. Start with "what can you tell me about this site's plugins?"
The site must be publicly reachable over HTTPS with pretty permalinks enabled. Clients on revision 2026-07-28 get a 24-hour freshness hint on tools/list, so a tool added by a plugin update appears within a day on its own; older revisions have no expiry signal, so reconnect the connector after updating to pick up new tools.
Contributing
The easiest genuinely useful contribution is a pull request against
includes/data/prefix-overrides.json — the curated map from plugin slugs to the option/table prefixes they actually use (Contact Form 7 → wpcf7_). Every entry improves attribution accuracy for every user. See CONTRIBUTING.md.
Development
composer install # dev-only: PHPCS + WordPress Coding Standards (pinned)
composer lint
php tests/mcp-client.php https://example.com/wp-json/auditra/v1/mcp/{token}
tests/mcp-client.php is the CLI harness that exercises the endpoint without an AI client in the loop; tests/seed-conditions.sh builds a deliberately messy test site (and teardown-conditions.sh reverses it exactly). CI runs a PHP lint matrix (7.4–8.4), PHPCS, and a grep gate that fails the build if any write operation ever appears in the plugin code.
Security
See SECURITY.md for the supported versions and how to report a vulnerability privately.
License
GPL-2.0-or-later.
Auditra MCP questions
How do I connect Auditra to an AI client like Claude?
Enable the endpoint in wp-admin, generate a token, copy the HTTPS connection URL, and paste it into Claude under Settings -> Connectors -> Add custom connector.
Does the server provide scoring or advice on plugin issues?
No, the server only reports facts and leaves scoring and advice to the AI client.
What are the requirements for the WordPress site to work with Auditra?
The site must be publicly reachable over HTTPS and have pretty permalinks enabled.