MCP Server Contracts Are Untracked – Pinning Dependencies Isn't Enough

A developer discovered that pinning library versions in requirements.txt doesn't lock the actual contract an MCP server exposes to AI agents. Tool names, parameter shapes, and descriptions are generated dynamically from function signatures and docstrings. Without versioning or testing this contract, any code change can silently break integrations.