v1.3.0 ✨

The following security hardening changes are included:

• Default binding changed from 0.0.0.0 to 127.0.0.1: MCP server now binds to localhost by default for secure operation.
• Fail-closed network binding: SSE/HTTP startup is refused for non-loopback addresses unless MCP_ALLOW_INSECURE_NETWORK_BIND=true is explicitly set.
• Loopback-aware validation: IPv4, IPv6, IPv4-mapped IPv6, and localhost hostname forms are recognized.
• Secure deployment guidance: Docker examples limit host publishing to loopback and explain same-network container access; the Kubernetes example includes the required transport, Service, and restrictive NetworkPolicy.
• Updated onboarding and configuration examples: Documented setup paths now use secure defaults and explain the explicit override.
• Comprehensive security notice: Documentation explains the lack of MCP client authentication, network exposure risks, migration requirements, and recommended mitigations.
• Regression coverage: Unit tests cover secure defaults, environment parsing, SSE/HTTP loopback handling, fail-closed behavior, explicit override behavior, and STDIO behavior.
• Proof-of-concept status: Disclaimers explicitly state that this is example code and requires security review before production use.

Compatibility impact: This is an intentional security-hardening behavior change. Existing SSE/HTTP deployments with a non-loopback MCP_HOST will refuse to start until appropriate authentication/network controls are applied and MCP_ALLOW_INSECURE_NETWORK_BIND=true is set. Loopback and STDIO deployments require no migration.

v1.2.0 ✨

• The MCP server now supports Direct RPC connectivity to your RADKit server
• Documentation was updated to reflect all the connectivity and auth methods available
• Minor bugs fixed: Hardcoded sse mode

v1.1.0 ✨

v1.1.0

• Update of pip server to https://radkit.cisco.com/pip
• Update of radkit libraries to v1.9.6
• Update of python version to >=3.12,<3.13