mcp-registry-monitoring-guide

mcp-registry-monitoring-guide is a skill for Claude Code, Codex from nirholas/three.ws. It costs 67 tokens per session (850 once invoked), scanned A, original, Apache-2.0.

A monitoring guide for the MCP Registry, a catalogue of servers that connect AI assistants to tools and data. It can report when servers are added, changed, or removed through channels such as Slack, email, Discord, Telegram, Teams, webhooks, or RSS.

In plain words
What is it for?
Watching registry updates, sending notifications, querying changes through its CLI, REST API, Go SDK, or MCP server, and connecting alerts to team communication tools.
Why use it?
It removes the need to repeatedly check the registry for changes that may affect available integrations.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Watching registry updates, sending notifications, querying changes through its CLI, REST API, Go SDK, or MCP server, and connecting alerts to team communication tools.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nirholas/three.ws/mcp-registry-monitoring-guide
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add nirholas/three.ws --skill mcp-registry-monitoring-guide
Clone the repo
git clone --depth 1 https://github.com/nirholas/three.ws

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for mcp-registry-monitoring-guide

README.md
[![agentmods](https://agentmods.dev/badge/skills/nirholas/three.ws/mcp-registry-monitoring-guide/github.svg)](https://agentmods.dev/skills/nirholas/three.ws/mcp-registry-monitoring-guide)
Your own site
<a href="https://agentmods.dev/skills/nirholas/three.ws/mcp-registry-monitoring-guide"><img src="https://agentmods.dev/badge/skills/nirholas/three.ws/mcp-registry-monitoring-guide/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for mcp-registry-monitoring-guide

Your own site · 80×15
<a href="https://agentmods.dev/skills/nirholas/three.ws/mcp-registry-monitoring-guide"><img src="https://agentmods.dev/badge/skills/nirholas/three.ws/mcp-registry-monitoring-guide.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 850 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00067 $0.00850
Opus 5 $0.00034 $0.00425
Sonnet 5 $0.00013 $0.00170
Haiku 4.5 $0.00007 $0.00085

Measured 9d ago against content hash 79f9c1ee609f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

mcp-registry-monitoring-guide scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl http://localhost:8080/api/changes?since=24h
data/skills/development/mcp-registry-monitoring-guide/SKILL.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.

MCP Registry Monitoring Guide

MCP Notify monitors the official MCP Registry and alerts you when servers are added, updated, or removed. Stay on top of the MCP ecosystem without manual checking.

Notification Channels

Channel Setup Real-time
Discord Webhook URL
Slack Webhook URL
Telegram Bot token + chat ID
Email SMTP config
Microsoft Teams Webhook URL
Webhooks Custom URL
RSS Feed URL Polling

Quick Start

CLI

# Install
go install github.com/nirholas/mcp-notify@latest

# Monitor with Discord notifications
mcp-notify watch --discord-webhook "https://discord.com/api/webhooks/..."

# Monitor with Slack
mcp-notify watch --slack-webhook "https://hooks.slack.com/services/..."

# Monitor with Telegram
mcp-notify watch --telegram-token "bot123:ABC" --telegram-chat "-100123"

As MCP Server

MCP Notify itself runs as an MCP server, so AI agents can query registry changes:

{
  "mcpServers": {
    "mcp-notify": {
      "command": "mcp-notify",
      "args": ["serve"]
    }
  }
}

Tools available:

  • getNewServers — List recently added MCP servers
  • getUpdatedServers — List recently updated servers
  • getRemovedServers — List recently removed servers
  • searchRegistry — Search the registry by keyword
  • getServerDetails — Get full details for a specific server

REST API

# Get recent changes
curl http://localhost:8080/api/changes?since=24h

# Search registry
curl http://localhost:8080/api/search?q=crypto

# Get server details
curl http://localhost:8080/api/servers/sperax-crypto-mcp

Go SDK

import "github.com/nirholas/mcp-notify/sdk"

client := sdk.NewClient()
changes, err := client.GetChanges(sdk.Since(24 * time.Hour))
for _, c := range changes {
    fmt.Printf("[%s] %s: %s\n", c.Type, c.Server.Name, c.Server.Description)
}

Monitoring Strategies

Track Competitors

Monitor for MCP servers in your space:

mcp-notify watch --filter "crypto|defi|trading" --discord-webhook "..."

Read the full file on GitHub · 125 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 125 lines · 67 tokens per session scan A 79f9c1ee609f

Subscribe to this mod's changes

mcp-registry-monitoring-guide is a skill published in the GitHub repository nirholas/three.ws (114 stars, last pushed today), licensed Apache-2.0. It adds 67 tokens to every session and 850 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories