LabscoMCP early access ↗
nirholasMCP SERVER

MCP Notify

Search GitHub for MCP servers from your client, over a hosted endpoint with no install and no key.

by nirholas ↗MCP Plumbing: Proxies, Registries & InspectorsCommunity

LABSCO SUMMARY

A quick check of GitHub for an MCP server before you write one.

Both tools search GitHub's public repositories, so an assistant can answer "is there already a server for this?" with stars, license and last push in hand, and with nothing to install. They do not deliver the change alerts the project is named for; those come from the self-hosted service.

What it is

A project that watches the official MCP Registry for new, updated and removed servers and sends alerts to Discord, Slack, email, webhooks, RSS, Telegram or Microsoft Teams. Its MCP side is a hosted endpoint with two search tools; the alerting is a separate service you run yourself.

What you get

  • A keyword search of GitHub for MCP servers — search_mcp_servers
  • MCP repositories ranked by stars, as many as you ask for — list_mcp_servers
  • GitHub's own record for each result: description, stars, forks, topics, license, last push and whether it is archived

Requirements

Nothing to install and no key: add the hosted endpoint https://modelcontextprotocol.name/mcp/mcp-notify to a client that connects over HTTP. The alerting service is separate — docker compose or the ghcr.io/nirholas/mcp-notify image, with PostgreSQL 15 or newer — and its subscriptions are managed through its REST API, dashboard or CLI, not through these tools.

Setup effort

Add the hosted endpoint — paste it into your client