Connect WP Update Radar and your agent gets 2 tools, among them wp_update_radar_check, wp_update_radar_check_many. It answers at https://updates.utilityhouse.xyz/mcp/registry over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 12 September 2026; the last check, on 24 October 2026, succeeded.
WordPress plugin release signals from public support threads, with evidence and explicit unknowns.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
wp_update_radar_check | 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 th Inputs: plugin, version |
wp_update_radar_check_many | 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 verdi Inputs: plugins |
Every block below points at https://updates.utilityhouse.xyz/mcp/registry. Pick your client and copy.
claude mcp add --transport http wp-update-radar https://updates.utilityhouse.xyz/mcp/registry
{
"mcpServers": {
"wp-update-radar": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://updates.utilityhouse.xyz/mcp/registry"]
}
}
}{
"mcpServers": {
"wp-update-radar": {
"url": "https://updates.utilityhouse.xyz/mcp/registry"
}
}
}{
"servers": {
"wp-update-radar": {
"type": "http",
"url": "https://updates.utilityhouse.xyz/mcp/registry"
}
}
}{
"context_servers": {
"wp-update-radar": {
"url": "https://updates.utilityhouse.xyz/mcp/registry"
}
}
}{
"mcpServers": {
"wp-update-radar": {
"serverUrl": "https://updates.utilityhouse.xyz/mcp/registry"
}
}
}{
"mcpServers": {
"wp-update-radar": {
"url": "https://updates.utilityhouse.xyz/mcp/registry"
}
}
}name: WP Update Radar
version: 0.0.1
schema: v1
mcpServers:
- name: WP Update Radar
type: streamable-http
url: https://updates.utilityhouse.xyz/mcp/registry{
"mcpServers": {
"wp-update-radar": {
"httpUrl": "https://updates.utilityhouse.xyz/mcp/registry"
}
}
}{
"mcpServers": {
"wp-update-radar": {
"type": "http",
"url": "https://updates.utilityhouse.xyz/mcp/registry"
}
}
}{
"mcpServers": {
"wp-update-radar": {
"url": "https://updates.utilityhouse.xyz/mcp/registry"
}
}
}goose://extension?url=https%3A%2F%2Fupdates.utilityhouse.xyz%2Fmcp%2Fregistry&type=streamable_http&id=wp-update-radar&name=WP%20Update%20Radar
It answered our last check on 24 October 2026 in 222 ms. Over 6 checks since 12 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by utilityhouse.xyz and served from updates.utilityhouse.xyz, the vendor's own domain: https://updates.utilityhouse.xyz/mcp/registry.
2, as returned by the server's own tools/list on 23 September 2026: wp_update_radar_check, wp_update_radar_check_many.
It answered our last check on 24 October 2026 in 222 ms. Over 6 checks since 12 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://updates.utilityhouse.xyz/mcp/registry. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: xyz.utilityhouse.updates. Endpoint host: updates.utilityhouse.xyz. ARD identifier: urn:air:xyz.utilityhouse.updates:mcp:wp-update-radar.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.