WP Update Radar

Official2 tools

by updates

WordPress plugin release signals from public support threads, with evidence and explicit unknowns.

The MCP server xyz.utilityhouse.updates/wp-update-radar provides WordPress plugin release signals derived from public support threads. It includes evidence and explicit unknowns, and surfaces this information as tool outputs available through the server. It is intended for update-related visibility for WordPress plugins.

🛠️ Key Features

WordPress plugin release signals from public support threads
Includes evidence alongside explicit unknowns
Exposes 2 tools

🚀 Use Cases

Detect or monitor WordPress plugin release-related updates using support-thread information
Track what is known vs. unknown based on collected evidence

⚡ Developer Benefits

Tool-driven access to plugin update signals
Evidence/unknown handling supports programmatic decision-making

⚠️ Limitations

Signal source is limited to public support threads
Explicit unknowns indicate incomplete or unverified information

Captured live from the server via tools/list.

wp_update_radar_check_many

Answers: which of this site's plugin updates are risky right now? Prefer this over the single check whenever there is more than one plugin to look at — a whole site's plugin list costs one call here instead of one call each. Same five verdicts as the single check (known-bad, wait, update-now, too-new, insufficient-data), per item and independent: a plugin that is not indexed reports its own error and the rest still answer. Returns a count of each verdict, so the risky ones can be found without reading every row. Up to 25 plugins per call; more than that is reported, not silently cut. `insufficient-data` means this service does not know, which is not the same as safe. Not a security advisory and not a CVE lookup: it reports what other site owners are saying, which is a different question from whether a release is vulnerable. wordpress.org plugins only — premium plugins have no public forum to read, and themes are out of scope.

Parameters1

plugins

array

required

The plugins and the exact versions in use

Raw schema

{
  "type": "object",
  "properties": {
    "plugins": {
      "type": "array",
      "minItems": 1,
      "maxItems": 25,
      "description": "The plugins and the exact versions in use",
      "items": {
        "type": "object",
        "properties": {
          "plugin": {
            "type": "string",
            "description": "wordpress.org plugin slug, e.g. \"woocommerce\""
          },
          "version": {
            "type": "string",
            "description": "Exact release in use, e.g. \"8.5.1\""
          }
        },
        "required": [
          "plugin",
          "version"
        ],
        "additionalProperties": false
      }
    }
  },
  "required": [
    "plugins"
  ],
  "additionalProperties": false
}

wp_update_radar_check

Answers: is it safe to update this WordPress plugin to this version right now? Counts independent wordpress.org support-forum threads reporting trouble with that exact release against the plugin's own normal thread volume, and returns one of five verdicts with the threads behind it: known-bad multiple independent reports point at this release — hold wait some reports, above normal but not conclusive update-now report volume at or below this plugin's baseline too-new released under 48h ago; nobody has had time to hit problems insufficient-data not enough collected to judge — a gap here, NOT a finding about the release, and not a reason to reassure anyone Use it before applying a plugin update, or when someone asks whether a specific version broke anything. Not a security advisory and not a CVE lookup: it reports what other site owners are saying, which is a different question from whether a release is vulnerable. wordpress.org plugins only — premium and paid plugins have no public forum to read, and themes are out of scope. Covers the most-installed plugins; one outside that set returns an error rather than a guess.

Parameters2

plugin	string	required	wordpress.org plugin slug, e.g. "woocommerce"
version	string	required	Exact release to check, e.g. "8.5.1"

Raw schema

{
  "type": "object",
  "properties": {
    "plugin": {
      "type": "string",
      "description": "wordpress.org plugin slug, e.g. \"woocommerce\""
    },
    "version": {
      "type": "string",
      "description": "Exact release to check, e.g. \"8.5.1\""
    }
  },
  "required": [
    "plugin",
    "version"
  ],
  "additionalProperties": false
}

Install

Tools (2)

wp_update_radar_check_manywp_update_radar_check

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://updates.utilityhouse.xyz/mcp/registry

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "wp-update-radar": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://updates.utilityhouse.xyz/mcp/registry"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.