vault-mcp-client-cannot-reconnect-mid-session-use-filesystem

If vault-mcp disconnects mid-session, the MCP client will not reconnect even if the container is healthy. The fallback is direct filesystem inspection at /opt/second-brain/vault/ using Bash/Grep/Glob tools. Connectivity can be confirmed via a curl with sufficient timeout (5s was too short; TLS handshake requires more) — container health alone does not guarantee client-side session state.

Related

• docker
• 2026-04-04-oracle-001-self-architecture-analysis
• salesforce
• vault-mcp
• mcp-tool-cache-stale-after-mid-session-rebuild
• vault-mcp-client-session-scoped-wont-reconnect-mid-session
• vault-curl-5s-timeout-insufficient-for-tls-handshake
• vault-mcp-disconnected-mid-session-bypass-via-filesystem
• vault-mcp-session-scoped-disconnect-use-filesystem-fallback
• vault-mcp-curl-timeout-too-aggressive-for-tls-handshake