Summary

The MCP server detail modal in the public model hub displays the upstream URL that LiteLLM proxies to (for example: https://mcp.vendor.com/v1/vendor/mcp). This reveals internal infrastructure details to end users.

What is currently exposed to end users

- Upstream vendor URL (reveals which third-party service is being used) - Direct upstream endpoint (allows bypassing the LiteLLM proxy entirely if a token is obtained)

Why this is a problem

Exposing upstream endpoints and auth types leaks sensitive infrastructure information that should be restricted to administrators. An attacker gaining a token could use the direct upstream endpoint to bypass the proxy and reach the vendor API directly.

Expected behavior

The public model hub modal should only surface the LiteLLM-facing proxy endpoint (for example: https://your-litellm-host/<alias>/mcp). Upstream URLs and other backend configuration should be visible only in the admin panel.

Reproduction steps

1. Open the Public Model Hub UI (Model Hub -> MCP Hub tab). 2. Click an MCP server entry to open the MCP Server Details modal. 3. Observe the "URL" / "Usage Example" sections which include the upstream vendor URL and auth type…