# WP Update Radar (`utilityhouse/wp-update-radar`) Actor

Read-only beta with no seller event fee. Check release-specific WordPress.org plugin update risk with public evidence. Apify platform usage applies.

- **URL**: https://apify.com/utilityhouse/wp-update-radar.md
- **Developed by:** [UtilityHouse Team](https://apify.com/utilityhouse) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-usage

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

### What is WP Update Radar?

Check whether wordpress.org plugin releases are drawing unusual support-forum trouble reports before applying an update.

This Actor exposes a small, allowlisted set of **read-only MCP tools** through a normal Apify input form and API. It is intended for wordpress site owners, maintainers, agencies, and automation agents planning plugin updates. The Actor sends only the selected tool name and the JSON arguments you provide to the public UtilityHouse MCP endpoint, then writes one structured result to the run's default dataset.

### What can it do?

| Operation | Purpose |
|---|---|
| `wp_update_radar_check_many` | Check up to 25 plugin releases |
| `wp_update_radar_check` | Check one plugin release |

The Actor uses limited Apify permissions. It cannot alter the upstream product, your website, an order, a payment, a grant application, or a WordPress installation. An upstream HTTP error, MCP error, invalid response, or tool-level error fails closed and produces no successful-result event.

### How to use it

1. Choose an operation from the **Operation** field.
2. Paste the matching MCP arguments into **Tool arguments** as a JSON object.
3. Run the Actor and open **Results** in the default dataset.
4. Treat cited evidence and explicit unknowns as part of the answer; do not remove caveats when passing the result to another system.

Quick-start input:

```json
{
  "tool": "wp_update_radar_check_many",
  "arguments": {
    "plugins": [
      {
        "plugin": "woocommerce",
        "version": "11.0.1"
      }
    ]
  }
}
```

The same input can be used from Apify Console, the Apify API, schedules, webhooks, and supported integrations. Product details and current limitations are available at <https://updates.utilityhouse.xyz/>.

### Output

Every successful run writes exactly one dataset item:

```json
{
  "product": "wp-update-radar",
  "tool": "wp_update_radar_check_many",
  "eventCharged": false,
  "result": { "...": "The structured MCP result" }
}
```

The shape inside `result` follows the selected MCP tool. The Actor does not invent a success record when the upstream service refuses, abstains at protocol level, times out, or returns malformed data.

### Pricing and successful-result events

This public free beta does not charge a `successful_tool_result` event. Billing is disabled in the release configuration and also fails closed in code. A future paid release would require both an owner-controlled billing switch and an explicit `structuredContent.billable: true` result; a missing or false marker, an abstention, and every failed call emit no successful-result event. The dataset's `eventCharged` field records the actual decision. Apify platform compute and storage usage may still apply according to the user's plan.

### Privacy and limitations

- It is not a security advisory or CVE lookup.

- It covers wordpress.org plugins, not premium plugins or themes.

- Insufficient data means unknown, not safe.

- Do not send customer details, order identifiers, payment data, credentials, or other personal information in the arguments object.

- Results are stored in the caller's Apify dataset and follow that account's retention settings.

- This is decision support, not legal, security, financial, or award advice.

### Support

Start with the product documentation at <https://updates.utilityhouse.xyz/>. Include the Actor name, selected operation, and a privacy-safe error code when reporting a problem. Never include API keys, customer data, wallet details, payment identifiers, or raw store records.

# Actor input Schema

## `tool` (type: `string`):

Choose the read-only MCP operation to run.

## `arguments` (type: `object`):

JSON object matching the selected operation. See the README for a safe example.

## Actor input object example

```json
{
  "tool": "wp_update_radar_check_many",
  "arguments": {
    "plugins": [
      {
        "plugin": "woocommerce",
        "version": "11.0.1"
      }
    ]
  }
}
```

# Actor output Schema

## `results` (type: `string`):

Items in the run's default dataset.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("utilityhouse/wp-update-radar").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("utilityhouse/wp-update-radar").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call utilityhouse/wp-update-radar --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,utilityhouse/wp-update-radar"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/x10lruiA5qyThRgnh/builds/CuhUiWPW3X5rjUGR3/openapi.json