MCP list_api_keys replies pass client checks
list_api_keys answers in claude.ai again. Every MCP tool now replies with exactly the fields its output schema declares.
From November 9, list_api_keys on the remote MCP server sent each key’s creator with two fields its output schema does not declare. A client that checks replies against the schema, claude.ai among them, refused the whole reply whenever a person had created a key in the workspace, so the agent got an error instead of the list.
Every tool that declares an output schema now passes its reply through that schema on the server. A reply carries the declared fields and nothing else, and its text copy is built from the same data. Our MCP tests now check replies the way claude.ai does, so a reply that drifts from its schema fails a test before it ships.
The fields list_api_keys declares are unchanged: name, prefix, scopes, creator name, timestamps and whether this session may revoke the key. The three key management tools work as before.
