Auditra WordPress MCP
Plugin MCP server for WordPress plugin audits.
What came back:
A contact form removed years ago had left 642 rows of names and email addresses in a database table. The privacy tools on the site couldn't see it — they only know about plugins that still exist.
An invoicing plugin deleted long ago was still loading 19 KB of settings on every single page view.
A CAPTCHA plugin was active and running faithfully — for a contact form plugin that was removed years back. Nothing on the site calls it.
Nineteen orphaned database tables from at least four plugins we'd forgotten ever existed.
The plugins screen showed 7 healthy plugins. The database remembered 6 more.
We built the tool that did this (Auditra — free, GPL, read-only, on the official plugin directory), but the bigger point stands whatever you use: if a site is more than a few years old, its database remembers plugins you've forgotten.
How do others handle this on inherited sites? Genuinely curious about your workflow.
Install from WordPress:
1 Comment
The gap between what the WordPress admin shows and what the database remembers is a strong observation. The examples make the problem feel much more concrete.