Skip to content

MCP Lightcast 0.3.1

Version 0.3.1 adds an HTTP health endpoint, verifies MCP operation behind nginx, and refreshes installation and Core LMI documentation. This is a compatible update from 0.3.0: Python 3.14 or newer is still required, and all 37 MCP tools remain available.

HTTP health checks

  • GET /health returns HTTP 200 with {"status":"ok"}. HEAD /health returns the same headers without a body.
  • Responses use Cache-Control: no-store; writes return HTTP 405. Host and Origin protection remains enabled.
  • The endpoint checks process liveness without authenticating to Lightcast, requesting a token, or consuming API quota. It exposes no account details or upstream errors.
  • Docker Compose now monitors its HTTP service with this endpoint.

The existing lightcast://server/health MCP resource remains a separate, explicit OAuth check. A successful HTTP probe does not establish Lightcast API availability or dataset access. See the health endpoint guide.

Reverse proxy support

The nginx deployment guide covers TLS termination, trusted hosts and origins, forwarding MCP headers, disabling SSE buffering, and optional path prefixes.

A real nginx integration suite verifies both the current 2026-07-28 and legacy 2025-11-25 MCP protocols over HTTPS at /mcp and /lightcast/mcp. Tests exercise health probes, discovery of all 37 tools, server resource reads, and a successful Core LMI tool call with null values and release metadata preserved. Untrusted Host and Origin headers are rejected, including attempts to bypass the Host check with a forwarded hostname.

The suite uses a verified temporary TLS certificate and synthetic OAuth/Core LMI responses on an isolated backend network. It consumes no real Lightcast quota. It validates transport behavior, not a production authentication gateway or live API entitlements; shared deployments still need inbound authentication.

Documentation and validation

The README and quick-start guide now install the published package directly, with pinned uvx, pip, Docker, and MCP client examples. A dedicated Core LMI section describes all five tools, account access, and practical example questions.

  • 103 offline tests passed, including five HTTP health tests; 19 opt-in tests were skipped in the ordinary suite.
  • 11 nginx integration tests passed separately and now run in the required Docker CI job.
  • Python 3.14 and 3.15 CI checks, lint, formatting, type checking, strict documentation builds, distribution checks, and workflow checks passed.

See testing instructions to repeat the proxy checks. Users upgrading from 0.2 should also read the 0.3 migration guide.

Install

uvx --python 3.14 mcp-lightcast@0.3.1 --env-file .env

Or run the published Linux amd64 container:

docker run --rm -i --platform linux/amd64 --env-file .env \
  ghcr.io/lawwu/mcp-lightcast:0.3.1

Docker also publishes the moving 0.3 and latest tags. Configure credentials using the quick-start guide.