Who it is forA security engineer watching an MCP registry for new or modified servers.
The problemRegistries change silently, and a modified server version can slip into use unnoticed.
The outcomeA JSON report listing added and removed server identities and changed fields between two captures.
What you need first
- Python with uv or pip, or Docker (no Python required)
- Optional: an LLM API key in .env for semantic analysis (default config targets DeepSeek)
- Optional MCP extra for skillspector mcp
Steps
- Capture the registry payload before and after as registry-before.json and registry-after.json
- Scan the first:
skillspector scan registry-before.json --mcp-registry --format json --output previous.json - Scan the second with --mcp-registry-compare previous.json and write compared.json
- Read the comparison object: added, removed, changed and unchanged_count
- Inspect raw records for anything under unmodeled_changes
Prompt for your agent
Using NVIDIA/SkillSpector registry mode, scan registry-before.json, then compare registry-after.json against it, and give me a table of added, removed and changed MCP servers with the fields that changed.
Caveat. A server absent from the current input is reported as removed, which does not prove it was removed from the registry.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for NVIDIA/SkillSpector and "Spot new or changed MCP servers between registry snapshots"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer