Model Context Protocol resources and the caching utility
Verified 2026-09-05 · 8 claims · sources tier 1 · 1 disputed
Also known as cacheable operations, resource template, resources/subscribe.
The Model Context Protocol caching utility enumerates 6 cacheable operations, including server discovery, the tools list, the prompts list, the resources list, the resource templates list, and resource read 8. Under the protocol's subscription model, the subscriptions listen stream replaces the former resources subscribe request, unifying resource subscriptions and tool list notifications under one filter-based mechanism 3.
Protocol operations and subscription mechanism
The caching specification defines 6 operations eligible for caching: server discovery, the tools list, the prompts list, the resources list, the resource templates list, and resource read 8. In the field, the caching page's freshness formula survives only as its first token in this corpus's extracted text and must be read from the raw payload 2.
The subscriptions listen stream replaces the earlier resources subscribe request, allowing resource subscriptions and tool list notifications to share a single filter-based mechanism instead of operating in parallel 3. Additionally, the subscriptions specification mandates that a server MUST NOT send notification types that the client has not explicitly requested 4.
Notification handling and specification differences
This is disputed, as the Resources page's list changed notification section lacks the clause carried by both the Tools and Prompts pages restricting delivery to clients holding a subscriptions listen stream 6. Furthermore, the message flow diagram on the Resources page omits a list changed flow entirely, whereas the diagram on the Prompts page displays one within an optional fragment 5.
The Resources page does not define what happens to a notifiable event that occurs when no client holds a matching subscription, containing no queueing, retention, or replay language across its prose, code samples, or diagrams 7.
See also
See also The MCP subscriptions listen stream and notification delivery. See also Whether a cached tool list defeats a change notification. See also The Model Context Protocol server discovery operation. See also Fidelity of the corpus text extraction pipeline.
Applicability
Across the claims in this article, the evidence covers Model Context Protocol Project, verified as of 2026-09-05. The deployment model is not covered by any claim in this article. Specific release numbers and region exclusions are not covered by any claim in this article.
What remains uncertain
Whether a cached tools list defeats a list changed notification is not covered by any claim in this article. The Resources page does not state what becomes of a notifiable event that occurs while no client holds a matching subscription, and its prose, code samples, and diagram contain no queueing, retention, or replay language 7. What becomes of an event with no subscriber is not covered by any claim in this article. Whether any host documents its own answer to the delivery gap is not covered by any claim in this article. Why the Resources page omits the delivery qualifier its siblings carry is not covered by any claim in this article. What invalidates a cached entry besides expiry is not covered by any claim in this article. How a cursor behaves when a page changes mid traversal is not covered by any claim in this article. What a resource template is is not covered by any claim in this article. Whether prompts carry the same delivery weaknesses as tools is not covered by any claim in this article.
See also
Parent of
- The Model Context Protocol server discovery operationstub — One of the six cacheable operations
- Whether a cached tool list defeats a change notificationstub — Whether caching defeats a change notification
Related to
- Fidelity of the corpus text extraction pipelinestub — A second extraction defect was found here
Scopes
- The MCP subscriptions listen stream and notification delivery — Resource subscriptions were folded into that stream
Referenced by
- Whether a cached tool list defeats a change notificationstub — Builds on the caching utility already recorded for the resources operations
- Stateful tools in the Model Context Protocol — Adjacent utilities in the same revision
Claims
| # | Claim | Status | Confidence | Verified |
|---|---|---|---|---|
| 1 | The Model Context Protocol caching page states that a relevant notification received while a cached response is still fresh invalidates that cached response, which should then be considered immediately stale. Model Context Protocol specification 2026-07-28, Caching · Interaction with Notifications, closing paragraph | fact | 0.90 | 2026-09-05 |
| 2 | The caching page's freshness formula survives only as its first token in this corpus's extracted text and must be read from the raw payload. Model Context Protocol specification 2026-07-28, Caching · Caching, freshness | field-pattern | 0.90 | 2026-09-05 |
| 3 | The subscriptions listen stream replaces the former resources subscribe request, so resource subscriptions and tool list notifications now share one filter-based mechanism rather than running in parallel. Model Context Protocol specification 2026-07-28, Subscriptions · Subscriptions | fact | 0.90 | 2026-09-05 |
| 4 | The subscriptions page states that a server MUST NOT send notification types the client has not explicitly requested. Model Context Protocol specification 2026-07-28, Subscriptions · Subscriptions | fact | 0.90 | 2026-09-05 |
| 5 | The Resources page's message flow diagram omits a list changed flow entirely while the Prompts page's diagram shows one inside an optional fragment. Model Context Protocol specification 2026-07-28, Resources · Resources message flow diagram compared with the Prompts diagram | fact | 0.60 | 2026-09-05 |
| 6 | The Resources page's list changed notification section lacks the clause that the Tools and Prompts pages both carry restricting delivery to clients holding a subscriptions listen stream. Model Context Protocol specification 2026-07-28, Resources · Resources, List Changed Notification compared with the Tools and Prompts pages | disputed | 0.60 | 2026-09-05 |
| 7 | The Resources page does not state what becomes of a notifiable event that occurs while no client holds a matching subscription; no queueing, retention or replay language appears in its prose, its code samples or its diagram. | fact | 0.90 | 2026-09-05 |
| 8 | The caching page enumerates 6 cacheable operations: server discovery, the tools list, the prompts list, the resources list, the resource templates list, and resource read. Model Context Protocol specification 2026-07-28, Caching · Caching, cacheable operations | fact | 0.90 | 2026-09-05 |
Sources
Model Context Protocol specification 2026-07-28, Caching
Model Context Protocol specification 2026-07-28, Resources
Model Context Protocol specification 2026-07-28, Subscriptions
Cite this page
APA
WarmTransfer. (2026, September 5). Model Context Protocol resources and the caching utility. WarmTransfer. https://warmtransfer.net/knowledge/mcp-resources-and-caching
BibTeX
@misc{warmtransfer-mcp-resources-and-caching,
title = {Model Context Protocol resources and the caching utility},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/mcp-resources-and-caching},
note = {Verified 2026-09-05}
}