MCP List-Cache Stamps Signal Intent, Not Verified Caching Behavior
The July 2025 Model Context Protocol spec introduced list-cache stamps — ttlMs and cacheScope fields on tools/list — modeled after HTTP Cache-Control headers. However, developers are cautioning that the presence of these stamps only confirms a server made a claim, not that the claim is accurate or enforceable. A server can return well-formed cache stamps while changing its tool catalog on the very next call, and a probe checking only for field presence will still pass. The distinction matters because HTTP itself never guaranteed identical responses from Cache-Control headers — MCP imported the vocabulary without importing a verification mechanism. Engineers working with the spec are advised to test each caching clause independently, ensuring that a companion 'liar' server fails for one specific reason at a time rather than masking partial failures through combined conditions.
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