Inbox Zero
Search Gmail and Outlook, save drafts, manage email rules, and view email stats.
Monitor MCP registry for new servers - Discord Slack notifications alerts
Pick the AI app you use, then copy the settings.
Passed 2/3 checks · Runs on your computer
First: which AI do you use?
Pick your app and the steps appear below.
Claude cannot connect MCP Registry Monitor yet
The maker has not listed install details in the MCP Registry yet
ChatGPT cannot connect MCP Registry Monitor yet
The maker has not listed install details in the MCP Registry yet
B · Others in Chat & email that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Claude Code cannot connect MCP Registry Monitor yet
The maker has not listed install details in the MCP Registry yet
Cursor cannot connect MCP Registry Monitor yet
The maker has not listed install details in the MCP Registry yet
VS Code cannot connect MCP Registry Monitor yet
The maker has not listed install details in the MCP Registry yet
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 12, 2026
The registry name was verified with the GitHub account nirholas, which owns the repo
Code last changed yesterday
GitHub could not identify the licence type; open the file to check
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 2 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed yesterday, and the latest version (1.0.0) reached the registry 10 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code.
In the same category: Inbox Zero, draw.io, TradingMCP
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Search Gmail and Outlook, save drafts, manage email rules, and view email stats.
Create draw.io diagrams in chat from Mermaid or XML, shown live and interactive. 10,000+ shapes.
Market analysis for AI assistants: screeners, multi-timeframe analysis, backtests, in-chat charts.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Real-time monitoring and notifications for the MCP Registry ecosystem.
Features • Quick Start • Docs • Deploy • Contributing
Never miss an MCP update again. MCP Notify monitors the official MCP Registry for changes and delivers instant notifications through Discord, Slack, email, webhooks, and more.
MCP Notify monitors the official MCP Registry for changes and delivers notifications through multiple channels. Track new servers, version updates, and removals across the entire ecosystem or filter to specific namespaces and keywords.
docker compose up -d) brings up the full stack┌────────────────────────────────────────────────────────────────┐
│ MCP Notify │ ├────────────────────────────────────────────────────────────────┤ │ │ │ ┌──────────┐ ┌──────────┐ ┌──────────────────────────┐ │ │ │ Poller │───▶│ Differ │───▶│ Notification Dispatcher │ │ │ └──────────┘ └──────────┘ └──────────────────────────┘ │ │ │ │ │ │ │ ▼ ▼ ▼ │ │ ┌──────────┐ ┌──────────┐ ┌──────────────────────────┐ │ │ │ Registry │ │ Snapshot │ │ Channels │ │ │ │ API │ │ Store │ │ ┌───────┐ ┌───────────┐ │ │ │ └──────────┘ └──────────┘ │ │Discord│ │ Slack │ │ │ │ │ │ └───────┘ └───────────┘ │ │ │ ▼ │ ┌───────┐ ┌───────────┐ │ │ │ ┌──────────┐ │ │ Email │ │ Webhook │ │ │ │ │PostgreSQL│ │ └───────┘ └───────────┘ │ │ │ └──────────┘ │ ┌───────┐ │ │ │ │ │ RSS │ │ │ │ │ └───────┘ │ │ │ └──────────────────────────┘ │ │ │ │ ┌──────────────────────────────────────────────────────────┐ │ │ │ REST API │ │ │ │ /subscriptions /changes /feeds /health /metrics │ │ │ └──────────────────────────────────────────────────────────┘ │ │ │ │ ┌──────────────────────────────────────────────────────────┐ │ │ │ Web Dashboard │ │ │ │ React + TypeScript + Tailwind + shadcn/ui │ │ │ └──────────────────────────────────────────────────────────┘ │ │ │ └────────────────────────────────────────────────────────────────┘
# Clone the repository
git clone https://github.com/nirholas/mcp-notify.git cd mcp-notify
cp .env.example .env
docker compose up -d
Once your instance is running, manage subscriptions through its REST API:
# Create a webhook subscription via API
curl -X POST http://localhost:8080/api/v1/subscriptions \ -H "Content-Type: application/json" \ -d '{ "name": "My DeFi Alerts", "filters": { "keywords": ["defi", "ethereum", "swap"], "namespaces": ["io.github.*"] }, "channels": [{ "type": "discord", "config": { "webhook_url": "https://discord.com/api/webhooks/..." } }] }'
# Install CLI
go install github.com/nirholas/mcp-notify/cmd/mcp-notify-cli@latest
mcp-notify-cli changes --since 24h
mcp-notify-cli watch --filter "defi,blockchain" --output json
mcp-notify-cli subscribe \ --discord-webhook "https://discord.com/api/webhooks/..." \ --filter "io.github.myorg/*"
git clone https://github.com/nirholas/mcp-notify.git
cd mcp-notify make build ./bin/mcp-notify --config config.yaml
docker pull ghcr.io/nirholas/mcp-notify:latest
docker run -p 8080:8080 -v $(pwd)/config.yaml:/app/config.yaml \ ghcr.io/nirholas/mcp-notify:latest
helm repo add mcp-notify https://YOUR_USERNAME.github.io/mcp-notify
helm install mcp-notify mcp-notify/mcp-notify \ --set config.registryUrl=https://registry.modelcontextprotocol.io \ --set notifications.discord.enabled=true
| Variable | Description | Default |
|---|---|---|
MCP_WATCH_REGISTRY_URL | MCP Registry API URL | https://registry.modelcontextprotocol.io |
MCP_WATCH_POLL_INTERVAL | Polling interval | 5m |
MCP_WATCH_DATABASE_URL | PostgreSQL connection string | Required |
MCP_WATCH_REDIS_URL | Redis connection string | Optional |
MCP_WATCH_API_PORT | API server port | 8080 |
MCP_WATCH_LOG_LEVEL | Log level (debug, info, warn, error) | info |
# config.yaml
server: port: 8080 host: "0.0.0.0" cors: origins: ["*"]
registry: url: "https://registry.modelcontextprotocol.io" poll_interval: 5m timeout: 30s retry_attempts: 3
database: url: "postgres://user:pass@localhost:5432/mcp_watch?sslmode=disable" max_connections: 25
redis: url: "redis://localhost:6379/0"
notifications: discord: enabled: true rate_limit: 30/min slack: enabled: true rate_limit: 30/min email: enabled: true smtp: host: "smtp.example.com" port: 587 username: "" password: "" from: "mcp-notify@example.com" webhook: enabled: true timeout: 10s retry_attempts: 3 rss: enabled: true items_per_feed: 100
telemetry: metrics: enabled: true port: 9090 tracing: enabled: false endpoint: ""
# Create subscription
POST /api/v1/subscriptions
GET /api/v1/subscriptions
GET /api/v1/subscriptions/{id}
PUT /api/v1/subscriptions/{id}
DELETE /api/v1/subscriptions/{id}
POST /api/v1/subscriptions/{id}/pause POST /api/v1/subscriptions/{id}/resume
# Get recent changes
GET /api/v1/changes?since=2025-01-01T00:00:00Z&limit=100
GET /api/v1/changes/{id}
GET /api/v1/changes?server=io.github.example/my-server
# RSS feed (all changes)
GET /api/v1/feeds/rss
GET /api/v1/feeds/atom
GET /api/v1/feeds/rss?namespace=io.github.*&keywords=defi
# Health check
GET /health
GET /ready
GET /metrics
Full API documentation available at /api/docs when running the server, or see api/openapi.yaml.
Rich embeds include:
Interactive messages with:
Configurable digest emails:
{
"event_type": "server.updated", "timestamp": "2025-01-04T12:00:00Z", "server": { "name": "io.github.example/my-server", "description": "An example MCP server", "version": "2.0.0", "previous_version": "1.5.0", "packages": [...], "remotes": [...] }, "changes": [ { "field": "version", "old_value": "1.5.0", "new_value": "2.0.0" }, { "field": "description", "old_value": "...", "new_value": "..." } ], "registry_url": "https://registry.modelcontextprotocol.io/v0/servers/io.github.example%2Fmy-server" }
| Document | Description |
|---|---|
| Architecture | System design, components, and data flow |
| API Reference | Complete REST API documentation |
| Deployment Guide | Docker, Kubernetes, and production setup |
| Notification Channels | Channel configuration and troubleshooting |
| Demo Guide | Hands-on walkthrough and examples |
| Contributing | Development setup and guidelines |
# Run unit tests
make test
make test-integration
make test-e2e
make test-coverage
We welcome contributions! Please see CONTRIBUTING.md for guidelines.
# Clone repo
git clone https://github.com/nirholas/mcp-notify.git cd mcp-notify
make deps
make dev-services
make d