MCP Change Sentinel

Catch MCP servers that change after you approved them

Problem

After users install and approve an MCP server, the server side can silently update tool definitions, permission scopes or behavior without any client-side notice. The pain point of catching MCP servers that change after approval points to a real trust gap in the current ecosystem.

Solution

A lightweight local proxy or browser extension periodically fetches the tool manifest and metadata of approved MCP servers, diffs them against the last snapshot, and raises a clear alert when new tools, parameter changes or permission expansions appear. Users can re-approve or revoke with one click.

Users

Developers using MCP servers locally or in team environments who care about supply-chain security.

MVP

Save local snapshots of approved MCP server tool manifests; periodically or manually fetch latest definitions and diff them; alert and label new or modified items; one-click re-approve or disable; export a change report for teams.

Revenue

Free for individuals; team plan per seat with centralized policy, alert integrations and audit logs.

Why now

The MCP ecosystem is exploding with third-party servers while trust tooling remains primitive. A change-detection tool is a natural wedge, and a simple snapshot diff makes a viable MVP for a solo developer.