# magento.watch

- Registry name: `watch.magento/magento-watch` · version 1.0.0
- Categories (automatic, keyword rules): Shops & products, Commerce & marketing, Code & repositories, Developer tools
- Authentication at last check: No auth
- Declared risk: Not declared (tools carry no read/destructive hints)
- Capabilities (declared by the server): resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=watch.magento%2Fmagento-watch
- Server page: https://mcpstation.net/s/watch.magento--magento-watch.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

- streamable-http: `https://magento.watch/mcp/api`

## Tools (as reported by the server, not verified)

- `get\_version`: 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 is
- `get\_all\_versions`: 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
- `get\_supported\_versions`: 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
- `get\_eol\_versions`: 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
- `check\_compatibility`: Check if a specific PHP, MySQL, or other dependency version is compatible with a Magento version
- `get\_latest\_version`: 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 re
- `get\_security\_bulletins`: 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.
- `get\_security\_bulletin`: 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.
- `check\_version\_security`: 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
- `find\_patch`: 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
- `get\_patch`: 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.
- `find\_upstream\_fix`: 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 versi
- `get\_upstream\_fix`: 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,

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html