Use MCPJam as an inspector, not the final client
MCPJam Inspector is useful for validating transport, OAuth, discovery, tool schemas and annotations before diagnosing an AI client. It does not prove that the eventual agent presents confirmations, selects tools correctly or handles failures well.
Start the inspector with the public Home MCP URL ending in /mcp:
npx @mcpjam/inspector@latest \
--url https://your-public-home-mcp-url/mcp \
--name "Hombee Home MCP" \
--oauth \
--tab servers
Complete Hombee sign-in, inspect the server capabilities and review the exact tool schemas. Begin with a read-only list or describe operation. Do not call a state-changing tool merely to prove that the transport works.
Interpret the result correctly
A successful Inspector connection proves request acceptance, authorization and MCP discovery for that Hombee account. It does not prove a production agent can complete the same workflow or that an external action reached its final state.
If OAuth fails, verify the exact endpoint and redirect flow before inspecting tools. If discovery works but a tool is absent, compare user, installation and enabled modules. After the protocol check, repeat the same read-only scenario in the actual client and review its confirmation and error behavior separately.


