Fix public Moshcode session MCP gateway and discovery - #118
Merged
Merged
Conversation
ThreatCrush Security Scan20 finding(s) HIGH/CRITICAL: 3 | MEDIUM: 13 | LOW: 4
Snippets are redacted; ThreatCrush never prints matched credential material. |
ralyodio
marked this pull request as draft
September 13, 2026 10:10
ralyodio
marked this pull request as ready for review
September 13, 2026 10:14
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
1 participant
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.
Moshcode's per-session MCP URLs use
moshcode.sh, but that host returned 404 for the share endpoint and OAuth discovery. Route the product host's share and metadata paths to the existing app service, preserving the canonical resource URL and keeping OAuth consent/token issuance onapp.moshcode.sh.The destination is fixed; other tenant hosts, account pages, and caller-controlled upstream URLs cannot enter this gateway. Validation: all 253 tests pass, production build passes, and the built Next server returned real upstream discovery metadata and preserved the 401 bearer challenge for an unauthenticated MCP POST. Coordinated with moshcoder/moshcode#497; deploy after its scoped server changes pass review.