### What happened?

The MCP gateway logs this warning on **every** tool call when the calling host sends an integer `progressToken`:

``` WARNING:LiteLLM:Could not capture host progress context: 'int' object is not subscriptable ```

Per the MCP spec, `progressToken` is `string | integer` ([schema.json#L2302-L2308](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/schema/2025-11-25/schema.json#L2302-L2308), represented as `str | int` in the Python SDK's `mcp/types.py`), so the integer branch is valid and spec-compliant.

In `litellm/proxy/_experimental/mcp_server/server.py`, the host-progress-capture block formats the token with:

```python verbose_logger.debug(f"Host progressToken captured: {host_token[:8]}...") ```

The `[:8]` slice assumes a string, so an integer token raises `TypeError: 'int' object is not subscriptable`. The surrounding `try/except` swallows it and re-surfaces it as the misleading "Could not capture host progress context" warning above.

Two notes on impact:

- The f-string is evaluated eagerly regardless of log level, so this fires even with debug logging disabled. - `host_progress_callback` is assigned *before* the failing log line, so p…