Security & Testing

utilityhouse.xyz

Assesses the risk of updating WordPress plugins to specific versions.

3 endpoints14 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.

ENDPOINT 2

https://app.utilityhouse.xyz/mcp

No auth detected

MCP server metadata

Name: agentready-woo
Version: 1.1.0

Capabilities

tools

Server instructions

Run a privacy-safe readiness scan against a public WooCommerce storefront. Store-bound shopping tools use /mcp/{store_id}.

Known tools 5

scan_woo_store_readiness

Check whether a public WooCommerce storefront is readable by shopping agents.

Inferred read-only

preflight_woo_store

Run a free passive WooCommerce Store Preflight.

Inferred read-only

start_woo_release_verification

Start an ownership-authorized Release Gate run.

Inferred read-only

get_woo_release_verification

Get a Release Gate run owned by the bearer token account.

Inferred read-only

claim_woo_release_result

Claim a completed Release Gate result once.

Inferred read-only

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.agentready-woo]
url = "https://app.utilityhouse.xyz/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "agentready-woo": {
      "type": "http",
      "url": "https://app.utilityhouse.xyz/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: agentready-woo
Remote MCP URL: https://app.utilityhouse.xyz/mcp

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": {
    "agentready-woo": {
      "url": "https://app.utilityhouse.xyz/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "agentready-woo": {
      "type": "http",
      "url": "https://app.utilityhouse.xyz/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "agentready-woo",
  "transport": "streamable-http",
  "url": "https://app.utilityhouse.xyz/mcp"
}

MCP Inspector

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

ENDPOINT 3

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

No auth detected

MCP server metadata

Name: federal-grant-evidence
Version: 1.3.2

Capabilities

toolsresources

Server instructions

Use this server to find current U.S. federal grant opportunities and screen one opportunity against a non-personal organization profile using cited official evidence. The analysis is available as a non-chargeable preview that says which evidence is unresolved. The complete evidence-pack tool is currently a limited free beta: it never requests payment and releases a result only after the complete hard-gate and versioned award-history result has been prepared. A future paid release is planned at USD 0.09 per complete result. It never determines legal eligibility, predicts an award, writes an application, or submits anything. The official opportunity record and application instructions remain the authority. This product uses the Grants.gov API but is not endorsed or certified by the U.S. Department of Health and Human Services. Each valid tool call increments one aggregate channel/tool/outcome counter; no caller identity, request body, or organization profile is stored in usage analytics. Only the separate opt-in actual-profile beta stores a derived pointer-only pack and attestation receipt for 30 days after explicit consent; it never stores the raw profile.

Known tools 7

get_grant_document_manifest

Use this when the user needs to know which official documents a U.

Inferred read-only

analyze_nofo_requirements

Use this after the document manifest, when the user needs the requirements stated inside a U.

Inferred read-only

compare_grant_amendments

Use this when the user needs to know what changed between revisions of a U.

Inferred read-only

search_federal_grants

Use this when the user needs to find current or forecasted U.

Inferred read-only

analyze_federal_grant

Use this when the user needs a sourced go/no-go pursuit screen for one U.

Inferred read-only

get_federal_grant_evidence_pack

Use this limited free-beta tool after search or preview when the user wants a complete, versioned hard-gate and award-history evidence pack for one U.

Inferred read-only

submit_federal_grant_profile_v2_beta

Use this opt-in free-beta tool only when the user wants to test opportunity 359701 against current actual non-personal organization, project, and readiness facts.

Inferred read-only

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.federal-grant-evidence]
url = "https://grants.utilityhouse.xyz/mcp/registry"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "federal-grant-evidence": {
      "type": "http",
      "url": "https://grants.utilityhouse.xyz/mcp/registry"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: federal-grant-evidence
Remote MCP URL: https://grants.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": {
    "federal-grant-evidence": {
      "url": "https://grants.utilityhouse.xyz/mcp/registry"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "federal-grant-evidence": {
      "type": "http",
      "url": "https://grants.utilityhouse.xyz/mcp/registry"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "federal-grant-evidence",
  "transport": "streamable-http",
  "url": "https://grants.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.