Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#2,516 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
65/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
api, frontend

Línea de trabajo

Start by reproducing the issue in the Web client with the listed Streamable HTTP steps, changing the server response between resources/read requests. Trace the resources/read request and its cache behavior, using the TTLms=10 detail as a starting point. Done means Fetch skill.get reflects the latest server data without restarting the server.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug
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).
Lenguaje dominante
TypeScript
Estrellas
11k
Forks
1.5k
Merge medio
5 h 18 min
PR fusionados (30 d)
130

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de modelcontextprotocol/inspector

Todos los issues de modelcontextprotocol/inspector

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.