RockScout AI for WordPress Plugin Directory

RockScout AI tells you what is happening on your WordPress site in language you can act on — which security gaps matter, what changed since last week, and what to do about it.

Vulnerability Scanner — Checks your installed plugins, themes, and WordPress core against the Wordfence Intelligence vulnerability database. For every match you get the severity, the affected versions, and the recommended action, sorted so the urgent ones come first. Matching runs entirely on your own site. Requires a free Wordfence Intelligence API key.

Plain-Language Explanations — For any finding, get an explanation of what the vulnerability actually means for your site, what the real-world risk is, what to do, and how urgently. Explanations are strictly grounded in the vulnerability record — no invented details. Requires an AI provider (see FAQ).

Activity Tracker — Automatically logs plugin updates, theme changes, content edits, media uploads, user role changes, and logins. When something looks different, you can see what changed and when instead of guessing.

Site Health Check — WordPress version, PHP version and end-of-life status, active plugins with pending updates, scheduled task status, recent errors, and database info in one place.

Site Assistant — Ask questions about your site in plain language: “What changed this week?”, “Are any plugins outdated?”, “Why is the site slow?”. The assistant reads your activity log, health data, and vulnerability findings to answer. Two ways to connect a provider: paste an API key directly in plugin settings (OpenAI, Anthropic, Google Gemini), or use the WordPress AI Client on WordPress 7.0+.

AI Agent Integration — Registers WordPress Abilities so MCP-compatible agents such as Claude Desktop or Cursor can read your site health, activity log, plugin status, and vulnerability findings. Read-only. Requires the MCP Adapter plugin.

What it helps with

Knowing which security gaps on your site actually matter, and which one to fix first

Seeing what changed after a site went live — updates, edits, logins — without digging through logs

Getting an answer in plain language instead of a technical dashboard

Works the same whether you look after one site or twenty.

How it works

Install and activate the plugin

Activity logging and the site health check start immediately — no configuration needed

Add a free Wordfence API key to enable vulnerability scanning

(Optional) Configure an AI provider for plain-language explanations and the site assistant

External Services Nothing is sent anywhere until you enable a feature that needs it. Activity logging, the site health check, and vulnerability matching all run entirely on your own site.

1. Wordfence Intelligence — vulnerability data feed Optional. Requires a free Wordfence API key, configured in RockScout AI → Settings.

Downloaded to your site: vulnerability records — title, CVE identifier, severity score, affected version ranges, and remediation guidance.

Uploaded: nothing. Your list of installed plugins, themes, and versions is never sent to Wordfence. All matching happens locally on your site.

Wordfence Intelligence — https://www.wordfence.com/threat-intel/ | Terms | Privacy

Vulnerability records include data from the MITRE CVE Program and from Defiant, Inc. Attribution is displayed with each record.

2. AI provider — explanations and site assistant Optional. Active only once you configure an AI provider, and only at the moment you send a message or click “Explain in plain language”. There is no background or scheduled AI request.

What is sent with a request:

Your question, as you typed it

A site summary: WordPress version, environment type, PHP version, time zone and local time, HTTPS status, site language, active theme, number of active plugins, number of pending updates, number of administrator accounts, and a count of vulnerability findings by severity

A summary of recent changes on the site: what changed, when, and the role of the account that made the change

Depending on what you asked about, one additional group of details may be included — for example plugin and theme names with version numbers, matched vulnerability records, recent lines from the PHP error log, scheduled task status, content counts, or upload and memory limits. Details unrelated to your question are not sent.

What is never sent:

Passwords or API keys

Usernames, display names, email addresses, or IP addresses

Post, page, or product content

Customer, order, or form submission data

Media files

A note on the error log: PHP error messages can contain absolute file paths from your server. Error log lines are included only when your question relates to errors or something being broken, and are limited to the last few entries.

RockScout AI does not operate a server of its own for these features. Requests go directly from your site to the provider you chose, and are subject to that provider’s terms:

OpenAI — https://openai.com | Terms | Privacy

Anthropic — https://www.anthropic.com | Terms | Privacy

Google Gemini — https://ai.google.dev | Terms | Privacy

When using the WordPress AI Client on WordPress 7.0+, requests are routed through whichever provider plugin you have installed, and that provider’s terms apply instead.

Troubleshooting Vulnerability scan fails with “rate limit reached” The Wordfence Intelligence API allows one request per 30 minutes on the free tier. Clicking Scan Now repeatedly will hit this limit.

Fix: Wait 30 minutes. The plugin enforces its own cooldown, and daily scans via WP Cron are unaffected. Saving your API key always succeeds even when the feed is temporarily unavailable.

Vulnerability scan takes a long time or times out The Wordfence production feed is roughly 120 MB. On slow connections or low-memory hosting the download may time out.

Fix: Ensure PHP max_execution_time is at least 120 seconds. The plugin raises the memory limit automatically. If the scan still times out from the admin button, it retries in the background via WP Cron.

Google Gemini: “You exceeded your current quota” (limit: 0) Google’s free tier API keys may have a quota of zero requests for new projects or accounts without billing enabled. This is a Google restriction, not a plugin bug.

Fix: Enable billing in the Google Cloud Console. Even on the free tier this raises the quota from 0 to 15 requests per minute. Alternatively switch to OpenAI or Anthropic in RockScout AI → Settings.

Google Gemini: “This model only supports Interactions API” Some newer Gemini models, such as deep-research and preview builds, do not support the standard generateContent endpoint used by this plugin.

Fix: The plugin clears its model cache and selects a compatible model on the next request. If the problem persists, set the model manually to gemini-2.5-flash in RockScout AI → Settings.

Site assistant shows “Not connected” No AI provider is configured. Go to RockScout AI → Settings and either paste an API key, or configure a provider in Settings → Connectors on WordPress 7.0+.

Scheduled scans are not running If DISABLE_WP_CRON is defined on your site, or WP Cron is not being triggered, daily refreshes will not happen. The site health data shows scheduled task status, including overdue tasks.

Fix: Use Scan Now manually, or configure a real server cron job to hit wp-cron.php.