Security & Testing

utilityhouse.xyz

Assesses the risk of updating WordPress plugins to specific versions.

1 endpoint2 known toolsFirst detected September 2, 2026Last detected September 2, 2026

ENDPOINT 1

https://updates.utilityhouse.xyz/mcp/registry

No auth detected

MCP server metadata

Name: wp-update-radar
Version: 1.0.0

Capabilities

tools

Server instructions

Answers whether a WordPress plugin release is breaking other people's sites, from wordpress.org support-forum volume for that exact version — the question a site owner has before clicking Update, and one no changelog answers. Use wp_update_radar_check_many when there is more than one plugin to check. A verdict describes reports observed so far, not a guarantee; `insufficient-data` means this service does not know, which is not the same as safe. It is not a security advisory and not a CVE lookup, it covers wordpress.org plugins rather than premium ones, and a plugin outside the tracked index returns an error rather than a guess.

Known tools 2

wp_update_radar_check_many

Answers: which of this site's plugin updates are risky right now?

Inferred read-only

wp_update_radar_check

Answers: is it safe to update this WordPress plugin to this version right now?

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

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

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: wp-update-radar
Remote MCP URL: https://updates.utilityhouse.xyz/mcp/registry

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "wp-update-radar",
  "transport": "streamable-http",
  "url": "https://updates.utilityhouse.xyz/mcp/registry"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.