# WP Update Radar (remote · updates.utilityhouse.xyz)

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

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `updates.utilityhouse.xyz`: 80/100 (this document), [markdown](https://verifymcp.io/servers/xyz-utilityhouse-updates-wp-update-radar/mcp-registry.md), [page](https://verifymcp.io/servers/xyz-utilityhouse-updates-wp-update-radar/mcp-registry)

## Channel facts

- Endpoint: `https://updates.utilityhouse.xyz/mcp/registry`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 692 tokens (~346/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the WP Update Radar MCP server?

WP Update Radar is a hosted endpoint at https://updates.utilityhouse.xyz/mcp/registry, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http xyz-utilityhouse-updates-wp-update-radar 'https://updates.utilityhouse.xyz/mcp/registry'
```

### Cursor

```json
{
  "mcpServers": {
    "xyz-utilityhouse-updates-wp-update-radar": {
      "url": "https://updates.utilityhouse.xyz/mcp/registry"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.xyz-utilityhouse-updates-wp-update-radar]
url = "https://updates.utilityhouse.xyz/mcp/registry"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xyz-utilityhouse-updates-wp-update-radar": {
      "type": "remote",
      "url": "https://updates.utilityhouse.xyz/mcp/registry",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add xyz-utilityhouse-updates-wp-update-radar --url 'https://updates.utilityhouse.xyz/mcp/registry' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  xyz-utilityhouse-updates-wp-update-radar:
    url: "https://updates.utilityhouse.xyz/mcp/registry"
```

### Netclaw

```json
{
  "McpServers": {
    "xyz-utilityhouse-updates-wp-update-radar": {
      "Transport": "http",
      "Url": "https://updates.utilityhouse.xyz/mcp/registry"
    }
  }
}
```

### Vellum

```bash
assistant mcp add xyz-utilityhouse-updates-wp-update-radar -t streamable-http -u 'https://updates.utilityhouse.xyz/mcp/registry'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 75, +6)

- [security improvement] HTTPS: unverified → pass
- [security improvement] DNSSEC: fail → pass

### 2026-09-09 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 68, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “wp_update_radar_check” rewrote its description, which is the text the model reads
- [functional] Server version: 1.0.0 → 1.0.1

## MCP tools (2)

### `wp_update_radar_check_many` (~227 tokens)

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.

Input parameters:

- `plugins` (array, required): The plugins and the exact versions in use

Output parameters:

- `counts` (object): verdict -> count, plus `error` for items that could not be judged
- `examined` (integer): how many were actually judged, after the per-call cap
- `requested` (integer)
- `results` (array)
- `skipped` (integer)

### `wp_update_radar_check` (~333 tokens)

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.

Input parameters:

- `plugin` (string, required): wordpress.org plugin slug, e.g. "woocommerce"
- `version` (string, required): Exact release to check, e.g. "8.5.1"

Output parameters:

- `attribution` (object): how many threads were tied to this release and to its baseline, by the same function
- `baseline` (number): average threads per release for this plugin
- `baselineReleases` (integer): how many other releases the baseline was drawn from
- `coverage` (object): how much of this plugin's forum could be attributed at all
- `freshness` (object)
- `lastCheckedAt` (integer): epoch ms this plugin's forum was last swept; 0 means never
- `reasonCodes` (array): finite reasons for the state
- `signal` (string): what the public forum showed. NO_OBSERVATION means nothing was comparable, which is not the same as nothing being wrong.
- `state` (string): what to do. Separate from `signal`, which is only what was observed.
- `strongEvidence` (integer): threads naming this exact version
- `threads` (array)
- `unknowns` (array): what this answer does not know. Never empty.
- `verdict` (string)
- `weakEvidence` (integer): threads in this version's window that named no version

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/xyz-utilityhouse-updates-wp-update-radar/mcp-registry#diagnostics

## Score history

- 2026-09-21: 80
- 2026-09-20: 80
- 2026-09-19: 79
- 2026-09-18: 79
- 2026-09-17: 78
- 2026-09-16: 78
- 2026-09-15: 77
- 2026-09-14: 77
- 2026-09-13: 76
- 2026-09-12: 76
- 2026-09-11: 75
- 2026-09-10: 69
- 2026-09-09: 69
- 2026-09-08: 68
- 2026-09-07: 68
- 2026-09-06: 68
- 2026-09-05: 67
- 2026-09-04: 67
- 2026-09-03: 66
- 2026-09-02: 66

## Common questions

### What is the WP Update Radar MCP server?

WP Update Radar is an MCP server listed in the public MCP registry as xyz.utilityhouse.updates/wp-update-radar. WordPress plugin release signals from public support threads, with evidence and explicit unknowns. This page covers its hosted endpoint (https://updates.utilityhouse.xyz/mcp/registry).

### Is the WP Update Radar MCP server safe to use?

WP Update Radar scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the WP Update Radar MCP server expose?

WP Update Radar exposes 2 tools: wp_update_radar_check_many, wp_update_radar_check. Their descriptions and schemas cost roughly 560 tokens of context every time the server is loaded.

### Does the WP Update Radar MCP server require authentication?

No. We connected to WP Update Radar without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the WP Update Radar MCP server still maintained?

WP Update Radar is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://updates.utilityhouse.xyz/mcp/registry
- Website: https://updates.utilityhouse.xyz/
- Changelog RSS feed: https://verifymcp.io/servers/xyz-utilityhouse-updates-wp-update-radar/mcp-registry.xml
- Changelog JSON feed: https://verifymcp.io/servers/xyz-utilityhouse-updates-wp-update-radar/mcp-registry.json
- HTML version of this page: https://verifymcp.io/servers/xyz-utilityhouse-updates-wp-update-radar/mcp-registry