MCP tools/list different per user: what Sume's list varies by

Yes, a Sume tools/list differs by credential. The MCP 2026-07-28 changelog says list endpoints "no longer vary per-connection" because protocol sessions are removed, but Sume's list is built from the request's surface: an OAuth mcp:read session sees read-only tools, while mcp:write or an API key sees the full hosted set.

The two are not in conflict: the spec change is about per-connection state, and a credential is part of each request. Spec text is from the MCP changelog; Sume's from the docs and source, read 2026-10-01.

What did the spec change?

The changelog removes protocol-level sessions and the Mcp-Session-Id header, and says tools/list, resources/list and prompts/list no longer vary per connection. Servers needing cross-call state use explicit handles passed as ordinary tool arguments.

What decides which tools a Sume session sees?

Why does a tool I expected not show up?

The docs say mutating and paid tools are hidden until the session has mcp:write or an API key. If a tool exists in the catalog but not in your list, check the scope first; see catalog shows a tool that is not in tools/list.

How should I cache the list?

Key any cache by credential, not just by URL. A read-only token and an API key hitting the same endpoint get different lists, so sharing one entry would show a tool the read-only token cannot call, or hide one the key can. Re-fetch after the scope changes, such as after the user grants write on consent.