Allow MCP server to bind to addresses other than 127.0.0.1

What is the feature you'd like to have?
Please add an option to configure which address the official MCP server binds to.

Right now, it appears to always bind to 127.0.0.1. It would be useful to be able to change this to 0.0.0.0, or potentially a specific IP/interface, while keeping 127.0.0.1 as the default.

Is your feature request related to a problem?
Yes. I want to run Binary Ninja on my workstation while accessing its MCP server from an AI agent running on another machine over Tailscale.

Currently the MCP server only listens locally:

$ ss -lntp | grep 24642
LISTEN 0 50 127.0.0.1:24642 0.0.0.0:* users:(("binaryninja",pid=10402,fd=38))

Because it is bound to 127.0.0.1, the other machine cannot connect to it directly.

Are any alternative solutions acceptable?
It is possible to work around this using an SSH tunnel, socat, a reverse proxy, or similar port forwarding.

However, having a native setting for the bind address would be much cleaner.

For example:

127.0.0.1 — local access only/default
0.0.0.0 — all interfaces
100.x.x.x — a specific interface such as the machine's Tailscale IP

Additional Information:
None

Start by locating the official MCP server's listener setup and the existing configuration for port 24642. Check how the server currently binds to 127.0.0.1, then trace the relevant startup path to determine where a configurable address belongs; done means supporting a specified address while retaining 127.0.0.1 as the default and verifying the listener with ss.