MCP Registry Monitor

What MCP Registry Monitor MCP server does

The MCP Registry Monitor MCP server tracks changes in the official MCP Registry at registry.modelcontextprotocol.io. It can identify newly published servers, updated entries, version changes, and removals. Monitoring can cover the full registry or be narrowed with namespace, keyword, and server-pattern filters.

Detected changes are retained with timestamps as an audit history. Notifications can be sent through Discord, Slack, email, generic HTTP webhooks, RSS/Atom feeds, Telegram, and Microsoft Teams. Email supports immediate, hourly, daily, and weekly digest schedules.

How it works

A polling process requests registry data at a configurable interval. A diffing stage compares the latest data with stored snapshots, determines which entries changed, and passes those events to a notification dispatcher. PostgreSQL stores persistence and change history; Redis can be used optionally for caching.

The service exposes a REST API for subscription management and operational endpoints such as changes, feeds, health, and metrics. A React and TypeScript dashboard provides a visual way to configure and monitor the service. The command-line client can check recent changes, stream watch output, and create subscriptions.

Setup and configuration

For a self-hosted deployment, clone the repository, copy .env.example to .env, configure the instance, and start the stack with Docker Compose. The dashboard is available on port 8080 by default. The project also provides Docker images, source builds requiring Go 1.22 or later, and a Kubernetes Helm deployment.

MCP_WATCH_DATABASE_URL is required for the PostgreSQL connection. MCP_WATCH_REGISTRY_URL defaults to the official registry, while MCP_WATCH_POLL_INTERVAL defaults to five minutes. Other documented settings control Redis, the API port, and log verbosity. Configuration can also be supplied through YAML, including polling timeouts, retry counts, database limits, notification channels, and telemetry.

Tools and capabilities

• Poll the MCP Registry on a schedule.
• Detect additions, edits, version changes, and removals.
• Filter subscriptions by keywords, namespaces, or patterns.
• Send notifications to supported chat, email, feed, webhook, and collaboration channels.
• Manage subscriptions through REST endpoints or the CLI.
• Query changes and service status through API endpoints.
• View configuration and monitoring data in the web dashboard.

The MCP Registry Monitor MCP server also includes a Go SDK and an OpenAPI specification for application integration, according to the project documentation.

Limitations and notes

The deployment requires PostgreSQL for persistence. Redis is optional rather than mandatory. The project is designed for monitoring the official MCP Registry and does not state that it monitors arbitrary registries by default. Notification delivery depends on configuring the relevant channel, such as a Discord webhook or SMTP server. Polling frequency, retries, rate limits, and feed size are configurable and affect how quickly changes are detected and delivered.