dsh-mcp-live-status

DSH's settings page can confirm that an MCP plugin is mounted, but it cannot answer the more critical question: did the server actually complete a handshake? Because mcp-client defaults to failOnStartupError: false, a server whose transport never connected still reports ACTIVE in every UI surface. You typically discover it is dead only when the agent attempts to invoke one of its tools mid-task.

dsh-mcp-live-status embeds a real-time status pill in the conversation composer's tool row. It cross-references the Loader's configured plugin tree against the tool registry's actual mcp____ registrations to surface five distinct states: connected, mounted-but-not-connected, starting, mount-failed, and disabled. Clicking the pill opens a read-only panel listing each server's transport type, tool count, and failure reason. The plugin is entirely zero-config and read-only—it never starts, stops, or reloads a server—and includes a heuristic redaction layer so that URI credentials and secret-named arguments are stripped before any data reaches the browser.

Best suited for users running one or more MCP servers under DSH's web profile, particularly those who have been burned by silent connection failures and want to see the full picture before hitting send.