Skip to content

Add OAuth authorization and native permission enforcement for MCP clients - #1

Open
ramhar wants to merge 29 commits into
DadaDevelopment:mainfrom
ramhar:contrib/mcp-oauth
Open

ramhar wants to merge 29 commits into
DadaDevelopment:mainfrom
ramhar:contrib/mcp-oauth

docs: a declared version is not an artifact identity

4251948
Select commit
Loading
Failed to load commit list.
GitGuardian / GitGuardian Security Checks failed Oct 24, 2026 in 36s

2 secrets uncovered!

2 secrets were uncovered from the scan of 29 commits in your pull request. ❌

Please have a look to GitGuardian findings and remediate in order to secure your code.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

Details

🔎 Detected hardcoded secrets in your pull request

  • Pull request #1: contrib/mcp-oauth 👉 main
GitGuardian id GitGuardian status Secret Commit Filename
- - Authentication Tuple b33a24b itest/repo_list_gate.py View secret
- - Base64 Basic Authentication 13e1db2 itest/oauth_controls.py View secret

🛠 Guidelines to remediate hardcoded secrets

  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.