_ registry / mcp streamable-http · checked 58m ago

magento-watch

https://magento.watch

Registry code: 06f2a8883bda59a8

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://magento.watch/mcp/api
protocol
streamable-http ·2024-11-05
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is magento-watch live?
Yes — it answered the hub's last check (checked 58m ago). It answered 100% of checks over the last 30 days.
Is magento-watch free to use?
Yes — the hub reached it with no key and no payment.
What tools does magento-watch have?
13 tools: get_version, get_all_versions, get_supported_versions, get_eol_versions, get_latest_version, get_security_bulletin, find_patch, get_patch, ….
Is magento-watch safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
998ms

last good check

priced tools
0

of 13 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 13 tools
1 open 12 never probed 1 of 13 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_security_bulletins open 57m ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "since": {
      "type": "string",
      "format": "date",
      "description": "Only return bulletins published on or after this date (YYYY-MM-DD)"
    },
    "severity": {
      "enum": [
        "critical",
        "important",
        "moderate"
      ],
      "type": "string",
      "description": "Only return bulletins of this severity"
    }
  }
}
    arguments 19 lines
  • get_version unknown never probed

    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)

    mcp-tool

    {
  "type": "object",
  "required": [
    "distribution",
    "version"
  ],
  "properties": {
    "version": {
      "type": "string",
      "description": "Version number (e.g., \"2.4.8\", \"2.4.7-p3\")"
    },
    "distribution": {
      "enum": [
        "magento-community",
        "magento-commerce",
        "mage-os"
      ],
      "type": "string",
      "description": "The Magento distribution"
    }
  }
}
    arguments 22 lines
  • get_all_versions unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "distribution"
  ],
  "properties": {
    "distribution": {
      "enum": [
        "magento-community",
        "magento-commerce",
        "mage-os"
      ],
      "type": "string"
    }
  }
}
    arguments 16 lines
  • get_supported_versions unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "distribution"
  ],
  "properties": {
    "distribution": {
      "enum": [
        "magento-community",
        "magento-commerce",
        "mage-os"
      ],
      "type": "string"
    }
  }
}
    arguments 16 lines
  • get_eol_versions unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "distribution"
  ],
  "properties": {
    "distribution": {
      "enum": [
        "magento-community",
        "magento-commerce",
        "mage-os"
      ],
      "type": "string"
    }
  }
}
    arguments 16 lines
  • get_latest_version unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "distribution"
  ],
  "properties": {
    "distribution": {
      "enum": [
        "magento-community",
        "magento-commerce",
        "mage-os"
      ],
      "type": "string"
    }
  }
}
    arguments 16 lines
  • get_security_bulletin unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Bulletin id (e.g., \"APSB24-40\")"
    }
  }
}
    arguments 12 lines
  • find_patch unknown never probed

    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".

    mcp-tool

    {
  "type": "object",
  "required": [
    "distribution",
    "version"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "Ranked mode only, default 10"
    },
    "query": {
      "type": "string",
      "description": "Free text: symptoms, error message, feature names, or a patch id"
    },
    "modules": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Module names with or without the magento/module- prefix"
    },
    "version": {
      "type": "string",
      "description": "Exact Magento version, e.g. \"2.4.7-p3\""
    },
    "categories": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "QPT category names"
    },
    "distribution": {
      "enum": [
        "magento-community",
        "magento-commerce",
        "mage-os"
      ],
      "type": "string"
    },
    "includeInapplicable": {
      "type": "boolean",
      "description": "Also rank patches that do not apply to this version; each hit keeps its real applicable flag"
    }
  }
}
    arguments 49 lines
  • get_patch unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Patch id, e.g. \"ACSD-56760\""
    },
    "version": {
      "type": "string",
      "description": "Optional version: includes install instructions and a bundle URL for all applicable non-deprecated files, or composer null when none apply. Without a version, returns the bare entry."
    },
    "distribution": {
      "enum": [
        "magento-community",
        "magento-commerce"
      ],
      "type": "string",
      "description": "Optional distribution for installation. Defaults to magento-commerce when a live Commerce file applies to the version, otherwise magento-community."
    }
  }
}
    arguments 24 lines
  • find_upstream_fix unknown never probed

    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".

    mcp-tool

    {
  "type": "object",
  "required": [
    "distribution",
    "version"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "Ranked mode only, default 10"
    },
    "query": {
      "type": "string",
      "description": "Free text: symptoms, error message, feature names, or an upstream fix id"
    },
    "fixedIn": {
      "type": [
        "string",
        "null"
      ],
      "description": "Only fixes first released in this version, e.g. \"2.4.9\"; null for fixes not in any release yet"
    },
    "modules": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Module names with or without the magento/module- prefix"
    },
    "version": {
      "type": "string",
      "description": "Exact Magento version, e.g. \"2.4.8-p3\""
    },
    "categories": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "QPT category names"
    },
    "distribution": {
      "enum": [
        "magento-community",
        "magento-commerce",
        "mage-os"
      ],
      "type": "string"
    },
    "includeExcluded": {
      "type": "boolean",
      "description": "Also return entries excluded as features, refactors or test-only changes; each hit keeps its excluded reason"
    }
  }
}
    arguments 56 lines
  • get_upstream_fix unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Upstream fix id, e.g. \"magento2-40867\""
    },
    "version": {
      "type": "string",
      "description": "Optional version: adds the code match for that version and the Composer bundle URL, or install null when the fix does not apply to it"
    },
    "distribution": {
      "enum": [
        "magento-community",
        "magento-commerce"
      ],
      "type": "string",
      "description": "Optional distribution for installation, default magento-community"
    }
  }
}
    arguments 24 lines
  • check_compatibility unknown 57m ago

    Check if a specific PHP, MySQL, or other dependency version is compatible with a Magento version

    mcp-tool

    {
  "type": "object",
  "required": [
    "distribution",
    "magentoVersion",
    "dependency",
    "dependencyVersion"
  ],
  "properties": {
    "dependency": {
      "type": "string",
      "description": "Dependency name (e.g., \"php\", \"mysql\", \"elasticsearch\", \"redis\")"
    },
    "distribution": {
      "enum": [
        "magento-community",
        "magento-commerce",
        "mage-os"
      ],
      "type": "string"
    },
    "magentoVersion": {
      "type": "string",
      "description": "Magento version (e.g., \"2.4.8\")"
    },
    "dependencyVersion": {
      "type": "string",
      "description": "Dependency version to check (e.g., \"8.3\", \"8.0\")"
    }
  }
}
    arguments 31 lines
  • check_version_security unknown 57m ago

    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-...".

    mcp-tool

    {
  "type": "object",
  "required": [
    "distribution",
    "version"
  ],
  "properties": {
    "version": {
      "type": "string",
      "description": "Version number (e.g., \"2.4.7\", \"2.4.7-p3\")"
    },
    "distribution": {
      "enum": [
        "magento-community",
        "magento-commerce",
        "mage-os"
      ],
      "type": "string"
    }
  }
}
    arguments 21 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 06f2a8883bda59a8.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/06f2a8883bda59a8/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/06f2a8883bda59a8/badge.svg)](https://brick.blue/agent/06f2a8883bda59a8?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.