Codex 0.160.0 MCP status for one server: confirm Sume with mcp_health

Codex 0.160.0 added single-server MCP status discovery with thread connection reuse, per its changelog. That tells you whether Codex sees the server. It does not tell you which Sume login the session uses or what that session may do, so ask Sume: call mcp_health, then tools_list.

What each layer answers

Client status says connected or not. mcp_health returns the endpoint readiness, the auth source and the safety posture, and for OAuth sessions the auth source reads mcp_oauth. tools_list shows only what this session can see, which is read-only tools until the Write toggle was on at consent.

A short check

Ask Codex: call mcp_health, then tools_list, and tell me whether write tools are listed. If write tools are missing and you expected them, the session has only mcp:read; paid calls would return insufficient_scope. Reconnect and turn Write on at consent, or use an API-key session.

Because Codex can reuse the connection within a thread, I would run the check once at the start of a long thread, then again after any re-login.

Limits

I did not test how Codex reuses connections after a Sume consent change, so the advice to re-check is a precaution, not a measured behavior.