# magento.watch (remote · magento.watch)

Magento Open Source, Adobe Commerce and Mage-OS releases, EOL, requirements, CVEs and patches

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `magento.watch`: 67/100 (this document), [markdown](https://verifymcp.io/servers/watch-magento-magento-watch/mcp-api.md), [page](https://verifymcp.io/servers/watch-magento-magento-watch/mcp-api)

## Channel facts

- Endpoint: `https://magento.watch/mcp/api`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 13 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1942 tokens (~102/item across 19 items; 13 tools + 6 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 78% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the magento.watch MCP server?

magento.watch is a hosted endpoint at https://magento.watch/mcp/api, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http watch-magento-magento-watch 'https://magento.watch/mcp/api'
```

### Cursor

```json
{
  "mcpServers": {
    "watch-magento-magento-watch": {
      "url": "https://magento.watch/mcp/api"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "watch-magento-magento-watch": {
      "type": "http",
      "url": "https://magento.watch/mcp/api"
    }
  }
}
```

### Codex

```toml
[mcp_servers.watch-magento-magento-watch]
url = "https://magento.watch/mcp/api"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "watch-magento-magento-watch": {
      "type": "remote",
      "url": "https://magento.watch/mcp/api",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add watch-magento-magento-watch --url 'https://magento.watch/mcp/api' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  watch-magento-magento-watch:
    url: "https://magento.watch/mcp/api"
```

### Netclaw

```json
{
  "McpServers": {
    "watch-magento-magento-watch": {
      "Transport": "http",
      "Url": "https://magento.watch/mcp/api"
    }
  }
}
```

### Vellum

```bash
assistant mcp add watch-magento-magento-watch -t streamable-http -u 'https://magento.watch/mcp/api'
```

### Other

```json
{
  "mcpServers": {
    "watch-magento-magento-watch": {
      "type": "http",
      "url": "https://magento.watch/mcp/api"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-16 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-15 (score 66, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-14 (score 66)

First indexed and scored.

## MCP tools (13)

### `get_version` (~109 tokens)

Get detailed information about a specific Magento/Adobe Commerce version including release date, EOL date, system requirements, and a security summary: `security.fixedBy` (security fixes already included in this version) and `security.vulnerableTo` (open bulletins that still need an upgrade or an isolated patch)

Input parameters:

- `distribution` (string, required): The Magento distribution
- `version` (string, required): Version number (e.g., "2.4.8", "2.4.7-p3")

### `get_all_versions` (~79 tokens)

Get all versions for a distribution with their lifecycle information. Each version carries `securitySummary` { status, requiredPatches, upgradeRequired }: `isSecureVersion` and `statusLabel` describe the support lifecycle only, so a supported version can still have open bulletins. Call check_version_security for the remedies.

Input parameters:

- `distribution` (string, required)

### `get_supported_versions` (~82 tokens)

Get only currently supported versions (not EOL, not future releases). Each version carries `securitySummary` { status, requiredPatches, upgradeRequired }: `isSecureVersion` and `statusLabel` describe the support lifecycle only, so a supported version can still have open bulletins. Call check_version_security for the remedies.

Input parameters:

- `distribution` (string, required)

### `get_eol_versions` (~78 tokens)

Get versions that have reached end-of-life. Each version carries `securitySummary` { status, requiredPatches, upgradeRequired }: `isSecureVersion` and `statusLabel` describe the support lifecycle only, so a supported version can still have open bulletins. Call check_version_security for the remedies.

Input parameters:

- `distribution` (string, required)

### `check_compatibility` (~108 tokens)

Check if a specific PHP, MySQL, or other dependency version is compatible with a Magento version

Input parameters:

- `dependency` (string, required): Dependency name (e.g., "php", "mysql", "elasticsearch", "redis")
- `dependencyVersion` (string, required): Dependency version to check (e.g., "8.3", "8.0")
- `distribution` (string, required)
- `magentoVersion` (string, required): Magento version (e.g., "2.4.8")

### `get_latest_version` (~77 tokens)

Get the latest stable version for a distribution. Each version carries `securitySummary` { status, requiredPatches, upgradeRequired }: `isSecureVersion` and `statusLabel` describe the support lifecycle only, so a supported version can still have open bulletins. Call check_version_security for the remedies.

Input parameters:

- `distribution` (string, required)

### `get_security_bulletins` (~86 tokens)

List Adobe/Magento security bulletins (CVEs), optionally filtered by severity or publish date. Use this to list critical bulletins since a given date, or to survey what has been disclosed.

Input parameters:

- `severity` (string): Only return bulletins of this severity
- `since` (string): Only return bulletins published on or after this date (YYYY-MM-DD)

### `get_security_bulletin` (~77 tokens)

Get one security bulletin by id, including a plain-text summary, its CVEs, severity, and which versions per distribution contain the fix. Use this when the user names a specific bulletin or asks which patch fixes a given CVE.

Input parameters:

- `id` (string, required): Bulletin id (e.g., "APSB24-40")

### `check_version_security` (~122 tokens)

Check whether a specific Magento/Adobe Commerce version is vulnerable to known security bulletins, and which version fixes it. A version is also vulnerable when the only remedy from Adobe is an isolated patch applied on top of that base release; fixedIn is then null. This is the tool to call when a user asks "is my Magento vulnerable" or "which patch fixes CVE-...".

Input parameters:

- `distribution` (string, required)
- `version` (string, required): Version number (e.g., "2.4.7", "2.4.7-p3")

### `find_patch` (~277 tokens)

Find Adobe Quality Patches Tool (QPT) patches for a Magento Open Source or Adobe Commerce version. With only distribution and version it lists every applicable patch. Add query (symptoms, error text, feature words or a patch id like ACSD-56760), modules (e.g. "catalog", "module-sales") or categories (QPT names like "Admin", "Catalog/Product") to get a ranked list with a 0-100 relevance score and the signals that matched. Covers quality patches only; for security fixes use check_version_security. List mode can return several hundred hits; pass query, modules or categories to rank and limit. Mage-OS is not a QPT target and always returns status "unknown".

Input parameters:

- `categories` (array): QPT category names
- `distribution` (string, required)
- `includeInapplicable` (boolean): Also rank patches that do not apply to this version; each hit keeps its real applicable flag
- `limit` (integer): Ranked mode only, default 10
- `modules` (array): Module names with or without the magento/module- prefix
- `query` (string): Free text: symptoms, error message, feature names, or a patch id
- `version` (string, required): Exact Magento version, e.g. "2.4.7-p3"

### `get_patch` (~146 tokens)

Get one Quality Patches Tool patch by id (e.g. "ACSD-56760") with every file variant, its Composer constraint, resolved applicable versions per distribution, modified files, prerequisites, documentation fields and the raw patch URL.

Input parameters:

- `distribution` (string): Optional distribution for installation. Defaults to magento-commerce when a live Commerce file applies to the version, otherwise magento-community.
- `id` (string, required): Patch id, e.g. "ACSD-56760"
- `version` (string): Optional version: includes install instructions and a bundle URL for all applicable non-deprecated files, or composer null when none apply. Without a version, returns the bare entry.

### `find_upstream_fix` (~338 tokens)

Community fixes merged into magento/magento2 after a release line was cut, with per-version applicability from git apply checks; not Adobe Quality Patches, for those use find_patch. With only distribution and version it lists, newest first, every upstream fix whose code applies cleanly to that version and that the version does not contain yet. Add query (symptoms, error text, feature words or an id like magento2-40867), modules or categories (QPT category names like "GraphQL", "Catalog/Product") to get a ranked list with a 0-100 relevance score and the signals that matched. fixedIn filters by the first release that contains the fix (null for fixes not in any release yet). Mage-OS always returns status "unknown"; a version outside the checked release tags returns status "unknown-version".

Input parameters:

- `categories` (array): QPT category names
- `distribution` (string, required)
- `fixedIn` (string|null): Only fixes first released in this version, e.g. "2.4.9"; null for fixes not in any release yet
- `includeExcluded` (boolean): Also return entries excluded as features, refactors or test-only changes; each hit keeps its excluded reason
- `limit` (integer): Ranked mode only, default 10
- `modules` (array): Module names with or without the magento/module- prefix
- `query` (string): Free text: symptoms, error message, feature names, or an upstream fix id
- `version` (string, required): Exact Magento version, e.g. "2.4.8-p3"

### `get_upstream_fix` (~197 tokens)

Community fixes merged into magento/magento2 after a release line was cut, with per-version applicability from git apply checks; not Adobe Quality Patches, for those use find_patch. Get one upstream fix by id (e.g. "magento2-40867") with its pull request, linked issues, first release containing it, per-tag code match, affected versions, touched packages and files, labels and triage scores. Pass version, and optionally distribution, to get the code match for that version and the Composer bundle URL when the fix applies to it.

Input parameters:

- `distribution` (string): Optional distribution for installation, default magento-community
- `id` (string, required): Upstream fix id, e.g. "magento2-40867"
- `version` (string): Optional version: adds the code match for that version and the Composer bundle URL, or install null when the fix does not apply to it

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/watch-magento-magento-watch/mcp-api#diagnostics

## Score history

- 2026-10-17: 67
- 2026-10-16: 67
- 2026-10-15: 66
- 2026-10-14: 66

## Common questions

### What is the magento.watch MCP server?

magento.watch is an MCP server listed in the public MCP registry as watch.magento/magento-watch. Magento Open Source, Adobe Commerce and Mage-OS releases, EOL, requirements, CVEs and patches. This page covers its hosted endpoint (https://magento.watch/mcp/api).

### Is the magento.watch MCP server safe to use?

magento.watch scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the magento.watch MCP server expose?

magento.watch exposes 13 tools: get_version, get_all_versions, get_supported_versions, get_eol_versions, check_compatibility, and 8 more. Their descriptions and schemas cost roughly 1,776 tokens of context every time the server is loaded.

### Does the magento.watch MCP server require authentication?

No. We connected to magento.watch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the magento.watch MCP server still maintained?

magento.watch is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://magento.watch/mcp/api
- Website: https://magento.watch/mcp
- Changelog RSS feed: https://verifymcp.io/servers/watch-magento-magento-watch/mcp-api.xml
- Changelog JSON feed: https://verifymcp.io/servers/watch-magento-magento-watch/mcp-api.json
- HTML version of this page: https://verifymcp.io/servers/watch-magento-magento-watch/mcp-api