Categories › Data & Databases › Files, spreadsheets, CSV & PDFs
Magento Open Source, Adobe Commerce and Mage-OS releases, EOL, requirements, CVEs and patches
Remote server: your requests and data go to magento.watch. Claude Code: claude mcp add --transport http magento-watch https://magento.watch/mcp/api · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
get_version — Get detailed information about a specific Magento/Adobe Commerce version including release date, EOL date, system requirements, and a securiget_all_versions — Get all versions for a distribution with their lifecycle information. Each version carries `securitySummary` { status, requiredPatches, upgrget_supported_versions — Get only currently supported versions (not EOL, not future releases). Each version carries `securitySummary` { status, requiredPatches, upgrget_eol_versions — Get versions that have reached end-of-life. Each version carries `securitySummary` { status, requiredPatches, upgradeRequired }: `isSecureVecheck_compatibility — Check if a specific PHP, MySQL, or other dependency version is compatible with a Magento versionget_latest_version — Get the latest stable version for a distribution. Each version carries `securitySummary` { status, requiredPatches, upgradeRequired }: `isSeget_security_bulletins — List Adobe/Magento security bulletins (CVEs), optionally filtered by severity or publish date. Use this to list critical bulletins since a gget_security_bulletin — Get one security bulletin by id, including a plain-text summary, its CVEs, severity, and which versions per distribution contain the fix. Uscheck_version_security — Check whether a specific Magento/Adobe Commerce version is vulnerable to known security bulletins, and which version fixes it. A version is find_patch — Find Adobe Quality Patches Tool (QPT) patches for a Magento Open Source or Adobe Commerce version. With only distribution and version it lisget_patch — Get one Quality Patches Tool patch by id (e.g. "ACSD-56760") with every file variant, its Composer constraint, resolved applicable versions 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 Qget_upstream_fix — Community fixes merged into magento/magento2 after a release line was cut, with per-version applicability from git apply checks; not Adobe QNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.