v0.4 — MCP endpoint hardening & rate limits

Improved endpoint reliability, request validation, per-client rate limiting, and clearer error responses across all SC Sentinel MCP endpoints.

Note: This is mock/placeholder content for demonstration purposes.

v0.4 focuses on making the MCP endpoint more reliable under load and harder to misconfigure.

Request validation

  • Strict schema validation on all incoming MCP requests — malformed context objects now return a structured 400 with a machine-readable error code rather than a generic server error
  • License key format is validated before any database lookup, reducing unnecessary latency on clearly invalid keys
  • Endpoint rejects requests with unknown MCP protocol versions with a clear error rather than silently misinterpreting them

Per-client rate limiting

  • Token-bucket rate limiting applied per license key, with configurable burst allowance
  • Licensed clients have a higher limit than the free tier; Enterprise plans get a dedicated limit configured at signup
  • Rate limit state is included in response headers (X-RateLimit-Remaining, X-RateLimit-Reset) so clients can back off gracefully

Reliability improvements

  • Health check endpoint now reports database and license-service connectivity separately, making it easier to diagnose partial outages in self-hosted deployments
  • Hosted endpoint moved to a redundant deployment; 99.9% uptime SLA now applies to all paid plans

Documentation

Updated reference docs are available at /docs. The MCP response schema reference and error code list have been expanded with examples for every error case.