MCP Registry Monitor
What it does
Monitor MCP registry for new servers - Discord Slack notifications alerts
- Connects –
- Account or key No key needed
- Category 聊天与邮件
安装
选择你使用的 AI 应用,然后复制设置。
通过 2/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
Claude 暂时无法连接 MCP Registry Monitor
开发者尚未在 MCP 注册表中填写安装方式
ChatGPT 暂时无法连接 MCP Registry Monitor
开发者尚未在 MCP 注册表中填写安装方式
你可以改用这些方式
B · 聊天与邮件 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
- Inbox Zero✓ ChatGPT
- draw.io✓ ChatGPT
- TradingMCP✓ ChatGPT
Claude Code 暂时无法连接 MCP Registry Monitor
开发者尚未在 MCP 注册表中填写安装方式
Cursor 暂时无法连接 MCP Registry Monitor
开发者尚未在 MCP 注册表中填写安装方式
VS Code 暂时无法连接 MCP Registry Monitor
开发者尚未在 MCP 注册表中填写安装方式
一览
它能做什么
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月13日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 nirholas 验证,该账户拥有此仓库
- ✓ 通过
仍在维护
代码最后更新于前天
- ! 注意
有许可证
GitHub 无法识别许可证类型;请打开文件自行查看
- – 不适用
端点有响应
它在你的电脑上运行,没有互联网端点
- – 不适用
使用 OAuth 登录
在你的电脑上运行,改用本地设置
- … 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行;我们只能读取互联网端点的工具列表
讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
用户评价
还没有评价
与“聊天与邮件”中的其他服务器比较i
- 星标数多于此分类中其他 2018 个服务器的 97%
- 发布到注册中心的时间比此分类中其他 2018 个服务器的 1% 更新
- 基础检查结果等于或优于此分类中其他 2018 个服务器的 51%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
MCP Registry Monitor 安全吗?
它在 3 项适用的基础检查中通过了 2 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端?
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
它还在维护吗?
GitHub 仓库最后更新于前天,最新版本(1.0.0)于10个月前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。
有什么可以替代它?
同一分类中有:Inbox Zero, draw.io, TradingMCP
同类别的其他选择
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
draw.io
Create draw.io diagrams in chat from Mermaid or XML, shown live and interactive. 10,000+ shapes.
TradingMCP
Market analysis for AI assistants: screeners, multi-timeframe analysis, backtests, in-chat charts.
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
MCP Notify
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.
✨ Features
Core Capabilities
- Real-time Monitoring: Poll the MCP Registry at configurable intervals
- Smart Diffing: Detect new servers, updates, version changes, and removals
- Flexible Filtering: Subscribe to specific namespaces, keywords, or server patterns
- Change History: Full audit trail of all detected changes with timestamps
Notification Channels
- Discord: Rich embeds with server details and direct links
- Slack: Interactive messages with action buttons
- Email: Digest emails (immediate, hourly, daily, weekly)
- Webhooks: Generic HTTP webhooks for custom integrations
- RSS/Atom: Subscribe via any feed reader
- Telegram: Bot notifications via Telegram Bot API
- Microsoft Teams: Adaptive Cards with full Teams integration
Deployment Options
- Docker Compose: One command (
docker compose up -d) brings up the full stack - Self-Hosted: Deploy your own instance via Docker or Kubernetes
- CLI Tool: One-off checks and local monitoring
Developer Experience
- REST API: Full API for programmatic subscription management
- Web Dashboard: Visual configuration and monitoring interface
- Go SDK: Embed in your own applications
- OpenAPI Spec: Generate clients in any language
🏗️ Architecture
┌────────────────────────────────────────────────────────────────┐
│ 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 │ │ │ └──────────────────────────────────────────────────────────┘ │ │ │ └────────────────────────────────────────────────────────────────┘
🚀 Quick Start
Self-Hosted with Docker
# Clone the repository
git clone https://github.com/nirholas/mcp-notify.git cd mcp-notify
Configure environment
cp .env.example .env
Edit .env with your settings
Start services
docker compose up -d
Access dashboard at http://localhost:8080
Create a Subscription
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/..." } }] }'
Using the CLI
# Install CLI
go install github.com/nirholas/mcp-notify/cmd/mcp-notify-cli@latest
Check for recent changes
mcp-notify-cli changes --since 24h
Watch with live output
mcp-notify-cli watch --filter "defi,blockchain" --output json
Subscribe to notifications
mcp-notify-cli subscribe \ --discord-webhook "https://discord.com/api/webhooks/..." \ --filter "io.github.myorg/*"
📦 Installation
Prerequisites
- Go 1.26+ (for building from source)
- PostgreSQL 15+ (for persistence)
- Redis 7+ (optional, for caching)
- Docker & Docker Compose (for containerized deployment)
From Source
git clone https://github.com/nirholas/mcp-notify.git
cd mcp-notify make build ./bin/mcp-notify --config config.yaml
Docker
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
Kubernetes
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
🔧 Configuration
Environment Variables
| 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 |
Configuration File
# 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: ""
📡 API Reference
Subscriptions
# Create subscription
POST /api/v1/subscriptions
List subscriptions
GET /api/v1/subscriptions
Get subscription
GET /api/v1/subscriptions/{id}
Update subscription
PUT /api/v1/subscriptions/{id}
Delete subscription
DELETE /api/v1/subscriptions/{id}
Pause/resume subscription
POST /api/v1/subscriptions/{id}/pause POST /api/v1/subscriptions/{id}/resume
Changes
# Get recent changes
GET /api/v1/changes?since=2025-01-01T00:00:00Z&limit=100
Get change details
GET /api/v1/changes/{id}
Get changes for specific server
GET /api/v1/changes?server=io.github.example/my-server
Feeds
# RSS feed (all changes)
GET /api/v1/feeds/rss
Atom feed (all changes)
GET /api/v1/feeds/atom
Filtered feed
GET /api/v1/feeds/rss?namespace=io.github.*&keywords=defi
Health & Metrics
# Health check
GET /health
Readiness check
GET /ready
Prometheus metrics
GET /metrics
Full API documentation available at /api/docs when running the server, or see api/openapi.yaml.
🔔 Notification Formats
Discord
Rich embeds include:
- Server name and description
- Change type (new, updated, removed)
- Version information
- Direct link to registry
- Package registry links (npm, PyPI, etc.)
Slack
Interactive messages with:
- Expandable server details
- Quick action buttons
- Thread support for related changes
Email Digest
Configurable digest emails:
- Immediate (per-change)
- Hourly summary
- Daily digest
- Weekly roundup
Webhook Payload
{
"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" }
📖 Documentation
| 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 |
🧪 Testing
# Run unit tests
make test
Run integration tests (requires Docker)
make test-integration
Run e2e tests
make test-e2e
Run all tests with coverage
make test-coverage
🤝 Contributing
We welcome contributions! Please see CONTRIBUTING.md for guidelines.
Development Setup
# Clone repo
git clone https://github.com/nirholas/mcp-notify.git cd mcp-notify
Install dependencies
make deps
Start development services
make dev-services
Run in development mode with hot reload
make d