AyeWatch vs Ray notifications
AyeWatch is an MCP server published by SRX9. Marketplaces we read that list it: 1 (Official MCP Registry). Ray notifications is an MCP server published by gege-mn. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  AyeWatch |  Ray notifications |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.0 Downloads/month (npm): 85 Downloads/week (npm): 12 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | AyeWatch | Ray notifications |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (ayewatch.ai/api/mcp) | Remote server (ray-api.gege.mn/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/srx9/ayewatch-mcp | github.com/gege-mn/ray-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-25 | Responded 6 days ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
AyeWatch
Manage AyeWatch monitors for topics and web pages, and the webhook that receives their alerts.
Ray notifications
Send email, push, Slack, Discord, Telegram and webhook notifications and manage templates with Ray.
How to run each
AyeWatch As a remote MCP server
claude mcp add --transport http ayewatch https://ayewatch.ai/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Ray notifications As a remote MCP server
claude mcp add --transport http ray-mcp https://ray-api.gege.mn/mcp --header "Authorization: Bearer <YOUR_RAY_API_KEY>"Requires: RAY_API_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of Ray notifications responded at the last daily check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of AyeWatch publish no settings it asks for, so we do not compare settings.
What it can do: AyeWatch · What it can do: Ray notifications · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.