mcp server versioning is going to be a nightmare in six months

We're running 6 MCP servers in production and already hit version conflicts twice this month. Server A updates its schema, breaks server B's assumptions, agent starts failing in weird ways. There's no standard for MCP server versioning, no way to declare compatibility, no way to test interactions between servers before deploying. Everyone is just shipping and hoping. How are other people handling this? Are you pinning versions? Running integration tests? Just dealing with the chaos? Feels like we're going to need something like semver + a compatibility matrix before this scales, but maybe I'm overengineering it and the answer is just better monitoring?