magento.watch
watch.magento/magento-watch · v1.0.0
Magento Open Source, Adobe Commerce and Mage-OS releases, EOL, requirements, CVEs and patches
MCPremoteno credentialsSecurityDeveloper tools
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 13 tools, protocol 2024-11-05 · checked 2026-10-17
Test & rating
A 89/100
What it does: 13 tools · 13 read, 0 write · Security, E-commerce, Files & storage
Test call get_security_bulletins: worked (1,021 ms)
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +4
- Read/write annotations: 0
- Safe test call: +20
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://magento.watch/mcp/apiTools
13 tools listed at last check
get_versionGet 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 isget_all_versionsGet 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_versionget_supported_versionsGet 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_versionget_eol_versionsGet 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 remediescheck_compatibilityCheck if a specific PHP, MySQL, or other dependency version is compatible with a Magento versionget_latest_versionGet 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 reget_security_bulletinsList 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_bulletinGet 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_securityCheck 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 afind_patchFind 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 categoriesget_patchGet 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_fixCommunity 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 versiget_upstream_fixCommunity 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,
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/watch.magento/magento-watch)