MCP Tool Change Sentinel

Watches MCP server tool lists and alerts when READMEs fall behind

Problem

MCP server tool lists change quietly: one server added 33 tools while its README stayed untouched, which can silently change how dependent AI agents behave. Developers currently rely on manual diffs or repeated doc checks and can't keep continuous track of many MCP servers at once.

Solution

A service that periodically fetches and diffs MCP server tool lists. Users register a server endpoint or config file; the service compares tool names, descriptions, and parameters, alerts via email or webhook on additions, removals, or edits, and keeps a timestamped change timeline.

Users

AI app developers using MCP clients like Claude Code or Cursor, agent platform operators, and MCP server authors

MVP

Register MCP server endpoint; periodically pull tool list; diff by tool name and parameters; alert via email or webhook on change; show timestamped change history

Revenue

Free for 2 servers; $9/month for 20 servers with team alert channels; add-on verified badge for MCP server authors

Why now

The MCP ecosystem is expanding fast and tool lists are becoming the real boundary of agent capability, yet the community just started posting manual diffs and no dedicated change monitor exists. It's a lightweight, timely build for a solo developer.