MCP tools/list repeating a cursor: Claude Code 2.1.295 and Sume

Claude Code 2.1.295 stops asking a server for the same tools page up to 20 times. Sume's tools/list returns one page with no nextCursor, so it never loops.

4 min readSume
All posts

Claude Code 2.1.295 (Oct 8) no longer asks an MCP server for the same page up to 20 times when the server keeps repeating a pagination cursor. Sume's hosted tools/list is not paginated: it returns { tools: [...] } in one response with no nextCursor, so this bug cannot happen against https://mcp.sume.com/mcp.

What was the bug?

A paginated MCP list answers with a cursor for the next page. A server that returns the same cursor again sends a client into a loop. Per the changelog, Claude Code used to request the same page up to 20 times; 2.1.295 stops that.

Claude Code changelog entry (read 2026-10-09)
VersionDateChange
2.1.295Oct 8 2026Servers that repeat a pagination cursor are no longer asked for the same page up to 20 times

Does Sume paginate tools?

No. In the server source, the tools/list handler returns the whole list in one response and sets no cursor. The initialize reply reports listChanged: false, so there is no push for a changed list either. The list you see depends on the session: OAuth mcp:read only shows read-only tools, while mcp:write or an API key shows the full hosted set.

What if your own MCP server paginates?

Check three things before you blame the client:

  • Each page returns a new nextCursor, or none on the last page.
  • Cursors do not depend on a clock or a random value that changes between identical requests.
  • The last page omits the cursor rather than returning an empty string.

How do you check the Sume tool list?

Call tools_list through your client and count the tools against the live list in MCP tools and gates. The docs say not to assume parity with the HTTP API, so use tools_list and tools_schema as the contract.

Sources

Related posts

More in Developers

All Developers posts

Written by Sume