You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Skill/get (resources/read) caches response (for example with TTL=10) #2516
v2 — current (@modelcontextprotocol/inspector@latest)
Which client?
Web
Inspector version
2.8.0
Node version
23.11.1
Operating system (and browser, for the web client)
Ubuntu 26.04
Transport
Streamable HTTP
MCP server under inspection
local php server
Steps to reproduce
Run inspector
Start the server
Select skills
click on the skill
get the response (TTLms was set to 10) -- ignore the one in screendump below
modify the server response data for the resources/read
click on "Fetch will skills/get
same response as step 5
Expected behavior
response in resources/read should reflect latest updated data
Actual behavior
Report older data.
Logs, errors, or screenshots
Only closing the server and reopening updates the data.
related issues
the messages tab does not show the response of the skill/get call, with an invalid skills.md file it reports a failure on the skill/get call, does not show the skills/get response but does show resources/read data
inspector does not show an feature to call the resources_directory_read call, so this call cannot be tested
Upon successful skills.md query, and then clicking on "fetch wil skill.get" result in an error w/o any details
Already prototyped a fix?
No response
Before you submit
I searched existing issues and this is not a duplicate.
This is not a security vulnerability report (those go through the private advisory process).
changed the title [-]Skill/get (resources/read) caches response and does not verify size[/-][+]Skill/get (resources/read) caches response (for example with TTL=10)[/+]on Sep 26, 2026
Severity 3 — skill fetch (resources/read) shows stale content until the server is restarted; the report also lists three adjacent gaps that may want their own issues
Urgency 2 — wanted eventually; workaround is reconnecting
Bonuses: +1 bug label
Board: #28, Status Incoming (awaiting maintainer review — no milestone yet).
Activity
[-]Skill/get (resources/read) caches response and does not verify size[/-][+]Skill/get (resources/read) caches response (for example with TTL=10)[/+]cliffhall commentedon Oct 12, 2026
Triage: Priority Medium (total 6)
resources/read) shows stale content until the server is restarted; the report also lists three adjacent gaps that may want their own issuesbuglabelBoard: #28, Status
Incoming(awaiting maintainer review — no milestone yet).Merge pull request #2694 from modelcontextprotocol/v2/fix/2516-skill-…
cliffhall commentedon Oct 12, 2026
Fixed by #2694 (merged into v2/main).
fix(web): re-read the viewed skill file on a skills/get fetch (modelc…