Skip to content

Skill/get (resources/read) caches response (for example with TTL=10) #2516

Closed

Description

@symdeb

Which version line?

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

  1. Run inspector
  2. Start the server
  3. Select skills
  4. click on the skill
  5. get the response (TTLms was set to 10) -- ignore the one in screendump below
  6. modify the server response data for the resources/read
  7. click on "Fetch will skills/get
  8. 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

  1. 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
  2. inspector does not show an feature to call the resources_directory_read call, so this call cannot be tested
  3. Upon successful skills.md query, and then clicking on "fetch wil skill.get" result in an error w/o any details
Image Image Image

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).

Activity

  1. 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
  2. cliffhall commented on Oct 12, 2026

    @cliffhall
    Member

    Triage: Priority Medium (total 6)

    • 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).

  3. added this to the v2.11.0 milestone on Oct 12, 2026
  4. self-assigned this
    on Oct 12, 2026
  5. added a commit that references this issue on Oct 12, 2026
  6. cliffhall commented on Oct 12, 2026

    @cliffhall
    Member

    Fixed by #2694 (merged into v2/main).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingv2Issues and PRs for v2

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions