WP Update Radar
REMOTE · UPDATES.UTILITYHOUSE.XYZ · SCANNED SEP 20
WordPress plugin release signals from public support threads, with evidence and explicit unknowns.
Available components
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. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · updates.utilityhouse.xyz
claude mcp add --transport http xyz-utilityhouse-updates-wp-update-radar 'https://updates.utilityhouse.xyz/mcp/registry'
{
"mcpServers": {
"xyz-utilityhouse-updates-wp-update-radar": {
"url": "https://updates.utilityhouse.xyz/mcp/registry"
}
}
} {
"servers": {
"xyz-utilityhouse-updates-wp-update-radar": {
"type": "http",
"url": "https://updates.utilityhouse.xyz/mcp/registry"
}
}
} [mcp_servers.xyz-utilityhouse-updates-wp-update-radar] url = "https://updates.utilityhouse.xyz/mcp/registry"
{
"$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 mcp add xyz-utilityhouse-updates-wp-update-radar --url 'https://updates.utilityhouse.xyz/mcp/registry' --transport streamable-http
mcp_servers:
xyz-utilityhouse-updates-wp-update-radar:
url: "https://updates.utilityhouse.xyz/mcp/registry" {
"McpServers": {
"xyz-utilityhouse-updates-wp-update-radar": {
"Transport": "http",
"Url": "https://updates.utilityhouse.xyz/mcp/registry"
}
}
} assistant mcp add xyz-utilityhouse-updates-wp-update-radar -t streamable-http -u 'https://updates.utilityhouse.xyz/mcp/registry'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 +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.
- 11 Sept 26 +6
- HTTPS: unverified → pass ▲ security
- DNSSEC: fail → pass ▲ security
- 9 Sept 26 +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.
- 8 Sept 26 0
- 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 security
- Server version: 1.0.0 → 1.0.1 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://updates.utilityhouse.xyz/mcp/registry
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=utilityhouse.xyz | CN=WE1,O=Google Trust Services,C=US | 29 Aug 2026 | 27 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | eacbeaf33707a08b0e7a9f19c6dbf446 |
| SANs: utilityhouse.xyz, updates.utilityhouse.xyz, *.updates.utilityhouse.xyz | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of updates.utilityhouse.xyz. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| utilityhouse.xyz. | present | 2371 | 13 | Verified |
| updates.utilityhouse.xyz. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self'; script-src-attr 'none'; style-src 'self' https://fonts.googleapis.com; style-src-attr 'none'; font-src 'self' data: https://fonts.gstatic.com; img-src 'self' data: blob: https:; media-src 'self'; connect-src 'self'; frame-src 'none'; form-action 'self' https://accounts.google.com; frame-ancestors 'none'; base-uri 'self'; object-src 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://updates.utilityhouse.xyz/mcp/registry | Verified | 200 | |
| http (plaintext) | http://updates.utilityhouse.xyz/mcp/registry | HTTPS enforced | 308 | https://updates.utilityhouse.xyz/mcp/registry |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
wp_update_radar_check ~333
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.
| Name | Type | Req | Description |
|---|---|---|---|
| plugin | string | yes | wordpress.org plugin slug, e.g. "woocommerce" |
| version | string | yes | Exact release to check, e.g. "8.5.1" |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | object | yes | how many threads were tied to this release and to its baseline, by the same function |
| baseline | number | yes | average threads per release for this plugin |
| baselineReleases | integer | yes | how many other releases the baseline was drawn from |
| coverage | object | yes | how much of this plugin's forum could be attributed at all |
| freshness | object | yes | – |
| lastCheckedAt | integer | yes | epoch ms this plugin's forum was last swept; 0 means never |
| reasonCodes | array | yes | finite reasons for the state |
| signal | string | yes | what the public forum showed. NO_OBSERVATION means nothing was comparable, which is not the same as nothing being wrong. |
| state | string | yes | what to do. Separate from `signal`, which is only what was observed. |
| strongEvidence | integer | yes | threads naming this exact version |
| threads | array | yes | – |
| unknowns | array | yes | what this answer does not know. Never empty. |
| verdict | string | yes | – |
| weakEvidence | integer | yes | threads in this version's window that named no version |
No examples provided.
wp_update_radar_check_many ~227
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.
| Name | Type | Req | Description |
|---|---|---|---|
| plugins | array | yes | The plugins and the exact versions in use |
| Name | Type | Req | Description |
|---|---|---|---|
| counts | object | yes | verdict -> count, plus `error` for items that could not be judged |
| examined | integer | yes | how many were actually judged, after the per-call cap |
| requested | integer | yes | – |
| results | array | yes | – |
| skipped | integer | yes | – |
No examples provided.
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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.