Implement header-based session verification logic #17
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.
Add header-based control to the MCP proxy server to allow clients to explicitly manage authentication, auto-payment, and x402 error handling.
This enables clients like the JS SDK CLI and browser-based wallets to specify how the
/mcpproxy should handle session verification (API key, MCP auth, or none), whether to engage the x402 auto-payment hook, and if x402 errors should result in an HTTP 420 status code for easier client-side processing. This provides a flexible control plane for diverse client needs.