MCP servers need two hashes: what the model reads vs what the package runs

mrpkk · reddit · 2026-10-25

A Reddit post argues most MCP server setups track neither of the two hashes worth pinning: the tools/list payload (names, descriptions, inputSchema) that the model actually reads, and the tarball hash/version of what actually runs. Each is blind to the other's failure mode — a description edited at runtime can change model behavior without touching code, while a swapped dependency can change behavior with byte-identical descriptions. The author asks what practitioners actually do: pin the tarball and re-scan tools/list on connect, or treat descriptions as config reviewed like code.

Original post →

More from coding & agent

coding & agent channel →