magento.watch
REMOTE · MAGENTO.WATCH
Magento Open Source, Adobe Commerce and Mage-OS releases, EOL, requirements, CVEs and patches
Available components
Last scanned (13 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Developer Tools
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. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1942 tokens (~102/item across 19 items; 13 tools + 6 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 +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.
- 15 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 14 Oct 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://magento.watch/mcp/api
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=magento.watch | CN=WE1,O=Google Trust Services,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | de0b846d7e8cbd7113e06b840f95af24 |
| SANs: magento.watch, extensions.magento.watch, *.extensions.magento.watch | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of magento.watch. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| watch. | present | 54769 | 8 | Verified |
| magento.watch. | present | 2371 | 13 | Verified |
| magento.watch. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://magento.watch/mcp/api | Verified | 200 | |
| http (plaintext) | http://magento.watch/mcp/api | HTTPS enforced | 301 | https://magento.watch/mcp/api |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_compatibility ~108
Check if a specific PHP, MySQL, or other dependency version is compatible with a Magento version
| Name | Type | Req | Description |
|---|---|---|---|
| dependency | string | yes | Dependency name (e.g., "php", "mysql", "elasticsearch", "redis") |
| dependencyVersion | string | yes | Dependency version to check (e.g., "8.3", "8.0") |
| distribution | string | yes | – |
| magentoVersion | string | yes | Magento version (e.g., "2.4.8") |
No output schema declared.
No examples provided.
check_version_security ~122
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-...".
| Name | Type | Req | Description |
|---|---|---|---|
| distribution | string | yes | – |
| version | string | yes | Version number (e.g., "2.4.7", "2.4.7-p3") |
No output schema declared.
No examples provided.
find_patch ~277
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".
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | QPT category names |
| distribution | string | yes | – |
| 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 | yes | Exact Magento version, e.g. "2.4.7-p3" |
No output schema declared.
No examples provided.
find_upstream_fix ~338
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".
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | QPT category names |
| distribution | string | yes | – |
| 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 | yes | Exact Magento version, e.g. "2.4.8-p3" |
No output schema declared.
No examples provided.
get_all_versions ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| distribution | string | yes | – |
No output schema declared.
No examples provided.
get_eol_versions ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| distribution | string | yes | – |
No output schema declared.
No examples provided.
get_latest_version ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| distribution | string | yes | – |
No output schema declared.
No examples provided.
get_patch ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| distribution | string | – | Optional distribution for installation. Defaults to magento-commerce when a live Commerce file applies to the version, otherwise magento-community. |
| id | string | yes | 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. |
No output schema declared.
No examples provided.
get_security_bulletin ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Bulletin id (e.g., "APSB24-40") |
No output schema declared.
No examples provided.
get_security_bulletins ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| severity | string | – | Only return bulletins of this severity |
| since | string | – | Only return bulletins published on or after this date (YYYY-MM-DD) |
No output schema declared.
No examples provided.
get_supported_versions ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| distribution | string | yes | – |
No output schema declared.
No examples provided.
get_upstream_fix ~197
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.
| Name | Type | Req | Description |
|---|---|---|---|
| distribution | string | – | Optional distribution for installation, default magento-community |
| id | string | yes | 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 |
No output schema declared.
No examples provided.
get_version ~109
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)
| Name | Type | Req | Description |
|---|---|---|---|
| distribution | string | yes | The Magento distribution |
| version | string | yes | Version number (e.g., "2.4.8", "2.4.7-p3") |
No output schema declared.
No examples provided.
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.
remote · magento.watch
claude mcp add --transport http watch-magento-magento-watch 'https://magento.watch/mcp/api'
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.