All servers · Other
WP Update Radar
xyz.utilityhouse.updates/wp-update-radar · v1.0.1
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Read-only (all tools declare readOnlyHint) |
| Capabilities declared | tools |
| Tool definitions | 2 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
WordPress plugin release signals from public support threads, with evidence and explicit unknowns.
Connect
streamable-http · https://updates.utilityhouse.xyz/mcp/registry
claude mcp add --transport http wp-update-radar https://updates.utilityhouse.xyz/mcp/registry{
"mcpServers": {
"wp-update-radar": {
"url": "https://updates.utilityhouse.xyz/mcp/registry"
}
}
}Tools as reported by the server
wp_update_radar_check_manyAnswers: 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-newp_update_radar_checkReports 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 wh
Website · JSON · Text for agents · Registry updated 2026-09-08