All four tools are reads against the public registry, so an assistant can answer "is there already a server for this?" and "what shipped this week?" with no key and no deployment. The alerting half — namespace and keyword filters fanning out to Discord, Slack, email, webhooks, RSS, Telegram and Teams — is a service you run yourself with PostgreSQL behind it, and its subscriptions are managed over its REST API rather than through these tools.
Two halves of one project. The MCP server, mcp-notify-mcp, gives an assistant read access to the official MCP Registry — search, per-server detail, the full list and ecosystem statistics. Beside it sits a self-hosted service that polls the same registry and pushes changes out to Discord, Slack, email, webhooks, RSS, Telegram or Microsoft Teams.
- Registry search by name or description, with a limit on how much comes back
- One server's record: description, version, repository with stars and forks, license, homepage and documentation links
- The whole registry listed, paged with limit and offset
- Ecosystem statistics: total servers, changes today and this week, new servers this week, and the most active categories
The MCP server is a Go binary: go install github.com/nirholas/mcp-notify/cmd/mcp-notify-mcp@latest, then point your client at the command mcp-notify-mcp. It reads the public registry, so there is no account and no key. The monitoring and notification half is a separate deployment — docker compose, or the ghcr.io/nirholas/mcp-notify image — with PostgreSQL 15 or newer for persistence, Redis 7 optionally for caching, its API and dashboard on port 8080, and the registry polled every 5m by default through MCP_WATCH_POLL_INTERVAL.
One command — docker compose up -d