Change default binding from 0.0.0.0 to 127.0.0.1 to align with security recommendations #738
+7
−7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change default server settings and all example code to bind to
127.0.0.1
rather than0.0.0.0
Motivation and Context
The official docs note that
This change attempts to make that behavior the default and reduce the chances of successful DNS rebinding attacks.
How Has This Been Tested?
Not tested.
Breaking Changes
This could be breaking in the scenario where users are relying on this default behavior to make the server accessible outside of localhost. An alternative would be to remove the change to src/mcp/server/fastmcp/server.py but keep the changes in example files and comments. That version would not be breaking.
Types of changes
Checklist
Additional context