Search / xyz.utilityhouse.updates/wp-update-radar
protogridR0· no sign-inWordPress plugin release signals from public support threads, with evidence and explicit unknowns.
v1.0.1 · active · website · descriptor JSON · versions
{
"mcpServers": {
"wp-update-radar": {
"type": "http",
"url": "https://updates.utilityhouse.xyz/mcp/registry"
}
}
}claude mcp add --transport http wp-update-radar https://updates.utilityhouse.xyz/mcp/registry[mcp_servers.wp-update-radar]
url = "https://updates.utilityhouse.xyz/mcp/registry"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"wp-update-radar": {
"type": "remote",
"url": "https://updates.utilityhouse.xyz/mcp/registry",
"enabled": true
}
}
}{
"mcpServers": {
"wp-update-radar": {
"type": "http",
"url": "https://updates.utilityhouse.xyz/mcp/registry"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=wp-update-radar&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vdXBkYXRlcy51dGlsaXR5aG91c2UueHl6L21jcC9yZWdpc3RyeSJ9"
}{
"servers": {
"wp-update-radar": {
"type": "http",
"url": "https://updates.utilityhouse.xyz/mcp/registry"
}
}
}{
"mcpServers": {
"wp-update-radar": {
"httpUrl": "https://updates.utilityhouse.xyz/mcp/registry"
}
}
}extensions:
"wp-update-radar":
enabled: true
name: "wp-update-radar"
type: streamable_http
uri: "https://updates.utilityhouse.xyz/mcp/registry"
timeout: 300
protocol.modernnewest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28protocol.statelessonly applies to 2026-07-28 serversprotocol.transportstreamable HTTPprotocol.list_ttlonly applies to 2026-07-28 serversauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_length1 tools have descriptions over 1,024 characters, which crowds the contexttools.schemasevery tool has an object input schematools.annotations2 of 2 tools declare readOnlyHint or destructiveHinttools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHinttools.token_costabout 838 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changesno tool changes in 30 daysstability.rug_pullno tool changed its meaning under the same namedeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packageNo tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+dns-namespace +website +reachable +uptime-94% ~updated-42d-ago -no-repository
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://updates.utilityhouse.xyz/mcp/registry streamable-http | none | yes | 94% | 384 ms | 2025-06-18 | 2026-10-20 |
wp_update_radar_checkread-only | 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. |
wp_update_radar_check_manyread-only | 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. |
Schemas: list_tools.
{
"name": "xyz.utilityhouse.updates/wp-update-radar",
"title": "WP Update Radar",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://updates.utilityhouse.xyz/mcp/registry",
"type": "streamable-http"
}
],
"version": "1.0.1",
"websiteUrl": "https://updates.utilityhouse.xyz",
"description": "WordPress plugin release signals from public support threads, with evidence and explicit unknowns."
}