Four of five MCP list adapters in Inspector dropped an empty-string pagination cursor and silently re-fetched page one

GitHub·medium signalXBlueskyLinkedInCopy link

modelcontextprotocol/inspector#2277 (merged 2026-09-06T21:55Z) fixes `core/mcp/inspectorClient.ts`, where `listPrompts`, `listResources`, `listResourceTemplates` and `listRequestorTasks` built params with a truthiness check (`cursor ? { cursor } : {}`) while `listTools` correctly used `cursor !== undefined`. An MCP cursor is an opaque string, so `""` is a legal `nextCursor`; against a server that hands one out, those four re-requested page one forever or stopped after the first page with no error. The repo's own `protocolReplay.ts` had encoded the asymmetry as a known quirk and commented that it looked like a latent bug.