Skip to content

magento.watch MCP server

watch.magento/magento-watchmagento.watchstreamable-httpv1.0.0Scanned

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

13 tools: 2 change things and 11 only read.

Tools: 0 delete, 0 irreversible, 2 write, 11 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the magento.watch MCP server can do

The magento.watch MCP server is published by magento.watch, a domain the MCP Registry verified. It has 13 tools. It can create or change data (2 tools: check_compatibility and check_version_security), but cannot delete data. 11 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 19, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

13 tools

Changes things 2Claude Code: ask
  • check_compatibilityCheck if a specific PHP, MySQL, or other dependency version is compatible with a Magento versionNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Check if a specific PHP, MySQL, or other dependency version is compatible with a Magento version
  • check_version_securityCheck whether a specific Magento/Adobe Commerce version is vulnerable to known security bulletins, and which version fixes it.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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-...".
Only reads 11Show 11 read-only tools
  • find_patchFind Adobe Quality Patches Tool (QPT) patches for a Magento Open Source or Adobe Commerce version.No findings

    Why it is in this group

    • The name "find_patch" says "find": a word for reading.
    Description, as the server wrote it
    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".
  • 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…No findings

    Why it is in this group

    • The name "find_upstream_fix" says "find": a word for reading.
    Description, as the server wrote it
    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".
  • get_all_versionsGet all versions for a distribution with their lifecycle information.No findings

    Why it is in this group

    • The name "get_all_versions" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_eol_versionsGet versions that have reached end-of-life.No findings

    Why it is in this group

    • The name "get_eol_versions" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_latest_versionGet the latest stable version for a distribution.No findings

    Why it is in this group

    • The name "get_latest_version" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_patchGet one Quality Patches Tool patch by id (e.g.No findings

    Why it is in this group

    • The name "get_patch" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_security_bulletinGet one security bulletin by id, including a plain-text summary, its CVEs, severity, and which versions per distribution contain the fix.No findings

    Why it is in this group

    • The name "get_security_bulletin" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_security_bulletinsList Adobe/Magento security bulletins (CVEs), optionally filtered by severity or publish date.No findings

    Why it is in this group

    • The name "get_security_bulletins" says "get": a word for reading.
    Description, as the server wrote it
    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_supported_versionsGet only currently supported versions (not EOL, not future releases).No findings

    Why it is in this group

    • The name "get_supported_versions" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_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…No findings

    Why it is in this group

    • The name "get_upstream_fix" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • 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…No findings

    Why it is in this group

    • The name "get_version" says "get": a word for reading.
    Description, as the server wrote it
    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)

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:21 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2024-11-05
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://magento.watch/mcp/api: tools/list returned 13 tools to an anonymous client, including check_compatibility (write), check_version_security (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http magento-watch https://magento.watch/mcp/api
claude mcp add --transport http magento-watch https://magento.watch/mcp/api

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__magento-watch__get_version",
      "mcp__magento-watch__get_all_versions",
      "mcp__magento-watch__get_supported_versions",
      "mcp__magento-watch__get_eol_versions",
      "mcp__magento-watch__get_latest_version",
      "mcp__magento-watch__get_security_bulletins",
      "mcp__magento-watch__get_security_bulletin",
      "mcp__magento-watch__find_patch",
      "mcp__magento-watch__get_patch",
      "mcp__magento-watch__find_upstream_fix",
      "mcp__magento-watch__get_upstream_fix"
    ],
    "ask": [
      "mcp__magento-watch__check_compatibility",
      "mcp__magento-watch__check_version_security"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as magento-watch. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/watch.magento/magento-watch/verify?hash=dd89d06054da527d4fe2645e0642d761dddad89668973bb8895c0c176bfd9a09" | jq -e '.changed == false'

Pinned hash dd89d06054da, from Nov 19, 2026, 11:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/watch.magento/magento-watch/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for watch.magento/magento-watch
[![Anlyon Radar](https://radar.anlyon.com/badge/watch.magento/magento-watch.svg)](https://radar.anlyon.com/servers/watch.magento/magento-watch)

Source: MCP Registry. Synced Oct 21, 2026, 18:55 UTC.

magento.watch MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the magento.watch MCP server safe?

No scan can promise that. What its definitions show: 13 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the magento.watch MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the magento.watch MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the magento.watch MCP server have?

13 tools: 2 write, 11 read. check_compatibility, check_version_security, get_version, get_all_versions, get_supported_versions, get_eol_versions, get_latest_version, get_security_bulletins and 5 more.

Does the magento.watch MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the magento.watch MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the magento.watch MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.