auth: verify MCP HTTP clients against the API key - #181
Merged
Merged
Conversation
The MCP server now gates its HTTP transports with a token verifier that requires the connecting client to present the API key, compared with hmac.compare_digest to match the FastAPI layer. The stdio transport is local and does not pass through the HTTP auth layer, so it keeps working unchanged. Raises the fastmcp floor to >=4.0.0, where the auth API used here is available.
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 MCP server now gates its HTTP transports with a token verifier that requires the connecting client to present the API key, compared with
hmac.compare_digestto match the FastAPI layer. The stdio transport is local and does not pass through the HTTP auth layer, so it keeps working unchanged.Raises the
mcpextra's fastmcp floor to>=4.0.0, where theauth=verifier API used here is available (2.x exposed a different auth surface).Verified against fastmcp 4.0.5 on the
streamable-httptransport: a client with no token and a client with a wrong token are both rejected, a client presenting the API key gets the full tool set, andstdiocontinues to list tools with no client token.