vault-mcp-disconnected-mid-session-bypass-via-filesystem

vault-mcp MCP client can show as disconnected mid-session (session-scoped state, won’t reconnect) even when the vault endpoint is fully reachable — a 5s curl timeout is too aggressive for the TLS handshake. When the MCP client reports disconnected, run integrity checks directly against the vault filesystem at /opt/second-brain/vault/ rather than retrying MCP tools. The container itself reports Up 30+ hours (healthy).

Related

• vault-mcp-client-cannot-reconnect-mid-session-use-filesystem
• docker
• 2026-04-04-oracle-001-self-architecture-analysis
• vault-mcp-client-session-scoped-wont-reconnect-mid-session
• salesforce
• vault-mcp-session-scoped-disconnect-use-filesystem-fallback
• vault-mcp-curl-timeout-too-aggressive-for-tls-handshake