[Bug] Dive assumes `tools` capability and fails when server is prompts-only

[vjik]

The Dive MCP host fails during initialization when connecting to MCP servers that do not implement the tools capability.

Even when a server explicitly provides only prompts functionality, the host still unconditionally calls:

tools/list

This leads to a hard failure if the server does not implement tools:

McpError: Method not found: tools/list

---

Expected behavior

The host should respect MCP capability negotiation and:

• Not call tools/list if the server did not advertise tools support
• Or gracefully handle Method not found responses for optional capabilities

---

Actual behavior

• Host always calls tools/list during initialization
• Assumes all MCP servers implement tools
• Fails initialization when tools are not present

---

Impact

• Prompts-only MCP servers cannot be used with Dive MCP host
• Breaks compatibility with partial MCP implementations
• Forces unnecessary implementation of no-op tools endpoints on servers

[kevinwatt]

Hi @vjik, thanks — this is related to #349 and is the concrete blocker for prompts-only servers. You're right: the host should respect capability negotiation and either skip tools/list when the server didn't advertise tools, or treat Method not found as a non-fatal response for optional capabilities.

We'll look at this together with #349. Appreciate the clear repro.