examples: bind auth-middleware server to localhost by default#784
Merged
maciej-kisiel merged 2 commits intomodelcontextprotocol:mainfrom Feb 11, 2026
Conversation
Contributor
Author
|
Local sanity check: |
Contributor
|
Thanks for the change. The same logic probably applies here as well: https://github.com/modelcontextprotocol/go-sdk/blob/main/scripts/server-conformance.sh#L74, could you adjust it as well? |
Contributor
Author
|
Pushed an update per your note: scripts/server-conformance.sh now binds the conformance server to loopback by default (localhost:) instead of : (all interfaces). |
maciej-kisiel
approved these changes
Feb 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The auth-middleware example currently defaults to
-http :8080, which binds to all interfaces (LAN-exposed) by default.This changes the default to
localhost:8080and adds a short comment noting-http 0.0.0.0:8080if you intentionally want to expose it.Rationale: this example serves token-generation endpoints and authenticated MCP routes; binding loopback by default avoids accidental exposure while keeping the opt-in remote behavior.