xyz.utilityhouse.updates/wp-update-radar

Est-ce que xyz.utilityhouse.updates/wp-update-radar est sûr ?

Au dernier audit MCP Hub, le serveur MCP « xyz.utilityhouse.updates/wp-update-radar » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 2 outils

• wp_update_radar_check≈ 1443 tokens

  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 theme, your premium plugins or your PHP version. `state` is what the evidence supports doing, `signal` is only what was observed: HOLD elevated public signal for this release WAIT above this plugin's own normal, or the window is still open GUARDED_ROLLOUT no elevated public signal — roll out somewhere low-stakes first NOT_ENOUGH_EVIDENCE too little was attributable to judge; a gap here, NOT a finding about the release, and not a reason to reassure anyone The legacy `verdict` field keeps its five strings (known-bad / wait / update-now / too-new / insufficient-data) for clients that already read it. Use it before applying a plugin update, or when someone asks whether a specific version broke anything. Not a security advisory and not a CVE lookup: it reports what other site owners are saying, which is a different question from whether a release is vulnerable. wordpress.org plugins only — premium and paid plugins have no public forum to read, and themes are out of scope. Covers the most-installed plugins; one outside that set returns an error rather than a guess.

  Paramètres, retour & exemple (2)

  Paramètres

  • plugin · string · requis
    wordpress.org plugin slug, e.g. "woocommerce"
  • version · string · requis
    Exact release to check, e.g. "8.5.1"

  Exemple d'appel

  {"name": "wp_update_radar_check", "arguments": {"plugin": "texte", "version": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"state": "GUARDED_ROLLOUT", "signal": "ELEVATED_PUBLIC_SIGNAL", "threads": [], "verdict": "known-bad", "baseline": 1, "coverage": {}, "unknowns": [], "freshness": {}, "attribution": {}, "reasonCodes": [], "weakEvidence": 1, "lastCheckedAt": 1}}

• wp_update_radar_check_many≈ 1438 tokens

  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 verdicts as the single check (known-bad, wait, update-now, too-new, insufficient-data), per item and independent: a plugin that is not indexed reports its own error and the rest still answer. Returns a count of each verdict, so the risky ones can be found without reading every row. Up to 25 plugins per call; more than that is reported, not silently cut. `insufficient-data` means this service does not know, which is not the same as safe. Not a security advisory and not a CVE lookup: it reports what other site owners are saying, which is a different question from whether a release is vulnerable. wordpress.org plugins only — premium plugins have no public forum to read, and themes are out of scope.

  Paramètres, retour & exemple (1)

  Paramètres

  • plugins · array · requis
    The plugins and the exact versions in use

  Exemple d'appel

  {"name": "wp_update_radar_check_many", "arguments": {"plugins": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"counts": {}, "results": [], "skipped": 1, "examined": 1, "requested": 1}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

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