[MCP] Enforce usage of caller-supplied API key#60
Merged
Conversation
adarshdigievo
approved these changes
Jul 6, 2026
adarshdigievo
left a comment
Member
There was a problem hiding this comment.
Thanks @vm-serpapi
Confirmed that API key override no longer works after this update.
Also, I pushed a commit to the branch removing workers argument in uvicorn.run() in server.py to fix WARNING: You must pass the application as an import string to enable 'reload' or 'workers'..
This was preventing server start when the server was started directly (uv run src server.py). The Dockerfile remains unchanged.
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
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.
Resolves serpapi/public-roadmap#3953
Changelog
Added enforcement of override of the caller-supplied API key. Also added tests to cover the override scenario.