Skip to content

Conversation

@dotmarn
Copy link
Contributor

@dotmarn dotmarn commented Jan 24, 2026

Motivation and Context

This PR addresses the issue #226

How Has This Been Tested?

Breaking Changes

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

@dotmarn dotmarn force-pushed the http-transport-header-compliance branch from 6b54958 to 3fa4be3 Compare January 24, 2026 14:49
@dotmarn dotmarn changed the title fix: [Server] HTTP Transport Header Compliance Fix: [Server] HTTP Transport Header Compliance Jan 24, 2026
@chr-hertel chr-hertel added the Server Issues & PRs related to the Server component label Jan 26, 2026
@Nyholm Nyholm force-pushed the http-transport-header-compliance branch from 3fa4be3 to 9906bbc Compare February 8, 2026 14:46
Copy link
Contributor

@Nyholm Nyholm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lovely.

I rebased the branch to fix the broken CI pileline

@chr-hertel chr-hertel merged commit f3ecb2e into modelcontextprotocol:main Feb 8, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Server Issues & PRs related to the Server component

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants