WP Update Radar

xyz.utilityhouse.updatesPublished by updates.utilityhouse.xyzOfficial publisherv1.0.1Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingDeveloper Tools

Overview

AI-generated overview

Surfaces WordPress plugin release signals drawn from public support threads, with evidence and stated unknowns.

What you can do
WP Update Radar is a remote MCP server that reports release signals for WordPress plugins, based on public support forum threads. It is described as providing evidence alongside each signal and flagging explicit unknowns, so an assistant can show where a claim came from and what is not known. No individual tools are listed in the supplied manifest.
When to use it
Useful when you want an assistant to check whether a WordPress plugin may be getting an update soon, and to see the public discussion behind that signal. Suited to plugin maintenance planning or research where sourcing and uncertainty matter.
Requirements
A remote streamable HTTP endpoint at the provider's address; no package install is needed. The manifest declares no authentication, environment variables, or headers, and no account or key is described.
Before you install
The server reads public support threads, so signals are second-hand and may be incomplete or wrong; the description itself notes explicit unknowns. No credentials, payments, or write actions are declared, but confirm the provider's data handling before relying on it.

Installation

In SourceWeft

  1. Open WP Update Radar in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/xyz.utilityhouse.updates%2Fwp-update-radar/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "wp-update-radar": {
      "type": "http",
      "url": "https://updates.utilityhouse.xyz/mcp/registry"
    }
  }
}

Tools

2

wp_update_radar_check_many

Check multiple WordPress plugin releases

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.

Parameterspluginsrequired

wp_update_radar_check

Check a WordPress plugin release

Reports what wordpress.org's public support forum says about one plugin release, compared with the releases before it, counted the same way on both sides. It does not answer whether an update is safe: nothing here can see your site, your theme, your premium plugins or your PHP version. `state` is what the evidence supports doing, `signal` is only what was observed: HOLD elevated public signal for this release WAIT above this plugin's own normal, or the window is still open GUARDED_ROLLOUT no elevated public signal — roll out somewhere low-stakes first NOT_ENOUGH_EVIDENCE too little was attributable to judge; a gap here, NOT a finding about the release, and not a reason to reassure anyone The legacy `verdict` field keeps its five strings (known-bad / wait / update-now / too-new / insufficient-data) for clients that already read it. 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.

Parameterspluginrequiredversionrequired

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.