Latest mcp inspector server version does not work with ToolHive

[dmjb]

See this PR: #996

When starting the latest version (0.16.0) the inspector spins endlessly waiting for the target server to become available.

Investigate the cause and make any necessary changes to allow us to use a newer server version.

Per @JAORMX 's comment on #996 - when we get to a point where we can update this, let's consider using renovate to keep it up to date.

[dmjb]

Diff of issues between 0.15 and 0.16: https://github.com/modelcontextprotocol/inspector/releases/tag/0.16.0

This looks noteworthy, but have not investiated it fully: modelcontextprotocol/inspector#529

[danbarr]

There was also a change from 0.14.0 -> 0.15.0, a proxy session token was introduced for security, which we're not accounting for.

It gets generated and displayed when you run via npx (and it does show up in our container log), but we should also add it to the URL we build:

Starting MCP inspector...
⚙️ Proxy server listening on 127.0.0.1:6277
🔑 Session token: fd1dfeddd07f5b88<snip>
Use this token to authenticate requests or set DANGEROUSLY_OMIT_AUTH=true to disable auth

🔗 Open inspector with token pre-filled:
   http://localhost:6274/?MCP_PROXY_AUTH_TOKEN=fd1dfeddd07f5b88<snip>

🔍 MCP Inspector is up and running at http://127.0.0.1:6274 🚀

[elsewhat-eq]

Had the same issue when running the latest version of inspector from a devcontainer and accessing the web interface from the OS.

Solved by setting environment variable HOST=127.0.0.1 before running
export HOST=127.0.0.1

The change of behaviour was introduced with https://github.com/modelcontextprotocol/inspector/pull/529/files