An MCP install snippet is often npx -y pkg. That pulls whatever is latest today. Tomorrow it can be another major.
After a server connects and a read-only call works, write the exact version you used. Prefer pkg@1.2.3 or a lock in your own wrapper.
Do not commit a floating tag into a shared mcp.json. The teammate who installs next week should get the same binary you audited.
If a server breaks after a client restart, check whether the package moved before you rewrite the config. Pair this with evaluate-MCP.