Shared MCP.Explicit controls.
The server rejects invalid requests before it processes them. It also stops if it cannot write a required audit record.
What shipped
- limits for request time, request size, and response size
- rejection of invalid origins, protocol versions, and JSON-RPC messages
- mandatory
--behind-proxyacknowledgement for non-loopback HTTP - atomic multi-file renames with recovery after a failed change
- protocol tests for the complete six-tool public MCP surface
- checksums, build provenance, a CycloneDX SBOM, notices, and signed OCI images
The release process now runs the complete native test battery before it publishes files or images. Cargo and MCP Registry publication use separate checks, so each public distribution has explicit evidence.