### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### The Feature

A mcp health checkpoint endpoint `/MCP_NAME/health` (or something similar to fit best practices) passthrough similar to the current mcp endpoint `/MCP_NAME/mcp`.

### Motivation, pitch

As far as I know, MCP doesn't have a universally standardized /health endpoint. But fastmcp has started supporting custom routes (https://gofastmcp.com/servers/server#custom-routes).

The `/health` endpoint is a conventional HTTP endpoint that custom MCP server implementations often include to indicate the server's operational status. A typical /health response might look like:

```json { "status": "ok", "uptime": 3600, "version": "1.0.0" } ```

It's used for:

- Liveness checks - Readiness checks - Load balancer / orchestration health probes

### What part of LiteLLM is this about?

Proxy

### LiteLLM is hiring a founding backend engineer, are you interested in joining us and shipping to all our users?

No

### Twitter / LinkedIn details

_No response_