HTTP standard headers + x-mcp-header

[maxisbey]

Tracks: #2715

The shared encode/decode and x-mcp-header rule helpers used by both sides; server-side validation of inbound headers vs body.

What's in it

• Encode/decode helpers for Mcp-Method/Mcp-Name/Mcp-Param-* (base64-sentinel, the x-mcp-header constraint rules).
• Server: validate inbound headers vs body, reject mismatches — wired in by New HTTP serving path (modern + dual-era) #2893.
• Client emit is owned by New Client (all-versions, low-level + high-level) #2894 (consumes these helpers).

Conformance

• (helpers — scenarios are owned by New HTTP serving path (modern + dual-era) server-side and New Client (all-versions, low-level + high-level) client-side)
• Together with New HTTP serving path (modern + dual-era) #2893: http-header-validation, http-custom-header-server-validation
• Together with New Client (all-versions, low-level + high-level) #2894: http-custom-headers, http-invalid-tool-headers, http-standard-headers

Dependencies

• Depends on: New HTTP serving path (modern + dual-era) #2893

References

• Transports — headers
• SEP-2243
• sep-2243.yaml
• python-sdk #2715

[maxisbey]

Done via #2974 (server-side validation + x-mcp-header filter) and #2990 (client Mcp-Param-* emit). Conformance waivers for SEP-2243 are zero in both baseline files.

_{AI Disclaimer}