Remote MCP · Endpoint

magento.watch MCP server

No. magento.watch answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://magento.watch/mcp/api

The last check completed an MCP handshake.

Registry name
watch.magento/magento-watch
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
847 ms
Tools exposed
13 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Magento Open Source, Adobe Commerce and Mage-OS releases, EOL, requirements, CVEs and patches
Listing
From the official MCP registry (active).
Recent checks of magento.watch
CheckedResultHandshake
4 hours agoHandshake completed847 ms
10 days agoHandshake completed665 ms
11 days agoHandshake completed637 ms
11 days agoHandshake completed680 ms
13 days agoHandshake completed46 ms
14 days agoHandshake completed423 ms
15 days agoHandshake completed824 ms
16 days agoHandshake completed45 ms
17 days agoHandshake completed715 ms
19 days agoHandshake completed507 ms
22 days agoHandshake completed421 ms
24 days agoHandshake completed57 ms
26 days agoHandshake completed946 ms
29 days agoHandshake completed498 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with magento.watch and makes no claim about it beyond what these checks measured.