watch.magento/magento-watch · v1.0.0 · security
magento.watch is healthy: it completed an MCP handshake in 1529 ms and exposes 13 tools.
Magento Open Source, Adobe Commerce and Mage-OS releases, EOL, requirements, CVEs and patches
Endpoint: https://magento.watch/mcp/api (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 13 |
| Latency | 1529 ms |
| Last checked (UTC) | 2026-10-15T14:30:25.152Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-15T14:30:25.152Z | Healthy | 1529 |
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, |