Study finds MCP servers often change behavior between versions without notice

A census of 21,643 servers in the official MCP registry found that 51% of multi-version servers changed what they advertise between releases, with 40.6% doing so silently. About 4.2% redirected their remote endpoint to a different host while keeping the same registry identity. The registry does not review code or scan for malware, checking only domain or repository ownership, and GitHub star counts were a weak safety signal. The article's author argues that one-time vetting cannot catch this drift and proposes runtime enforcement with signed, hash-chained call receipts and per-token tool restrictions, implemented in an open-source tool called CleiMesh.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in