Add native-tls feature for reqwest dependency

[anmatako]

This new feature avoids bringing the ring dependency that comes through even when using the reqwest-tls-no-provider feature

Motivation and Context

This change adds a new feature that entirely avoids the transitive ring dependency. Ring is not allowed in Microsoft's internal repos and use of rmcp is flagged by compliance.

How Has This Been Tested?

Tested in Codex agent from https://github.com/openai/codex

Breaking Changes

None

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

[alexhancock]

@anmatako This will need the commit message edited to conform to the https://www.conventionalcommits.org/en/v1.0.0/ format

I put in a pre-commit hook the other day to check this locally on commit, but perhaps you branched off from before?

#619

Sorry for the hassle!

[anmatako]

Moving to v0.13 avoids pulling ring. Native TLS may still be needed as a feature, but not blocking at the moment

[anmatako]

Alex, I actually closed the PR since the latest version allows to avoid "ring" without this native-tls feature. However, having the native-tls provider may still be useful so if you think that's valid I can reinstate the PR and amend the commit message. -- Antonis Matakos

…

On Fri, Jan 16, 2026 at 9:20 AM Alex Hancock ***@***.***> wrote: *alexhancock* left a comment (modelcontextprotocol/rust-sdk#622) <#622 (comment)> @anmatako <https://github.com/anmatako> This will need the commit message edited to conform to the https://www.conventionalcommits.org/en/v1.0.0/ format I put in a pre-commit hook the other day to check this locally on commit, but perhaps you branched off from before? #619 <#619> Sorry for the hassle! — Reply to this email directly, view it on GitHub <#622 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AST7EXZUHK6AETLRHST37L34HEMXHAVCNFSM6AAAAACR4E6EWCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTONRRGA2DCMJQHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[alexhancock]

Ok sounds good. Let's leave it at that with the solution in 0.13 then. Thanks!