scan_for_secrets

4 registry entries were observed exposing a tool named scan_for_secrets — none of them flagged as a privileged capability.

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 12,336 of 40,577 scannable entries (30%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.

  1. io.github.vladimirbakalov/secretguard-mcpMCPcommunitytrust 60/100 · B
    v0.1.4

    Scans code for hardcoded secrets (AWS, Stripe, GitHub, JWTs) before an AI agent commits it.

    io.github.vladimirbakalovUnknown2mo agoGitHubobserved · static extraction
    mcp

  2. Scans projects for secret exposure: leaked API keys, unprotected .env files, and secrets in logs.

    ClaudeCursorCopilotGemini
    io.github.vola-treblaUnknown4mo agonpmGitHubobserved · static extraction
    mcp
  3. secret-scanner-mcpMCPcommunitytrust 60/100 · B
    v0.1.1

    Scan a blob of code/text/diff for LEAKED SECRETS before you commit or share — API keys (AWS, GitHub, OpenAI, Stripe, Google, Slack…), tokens, private keys (RSA/EC/SSH/PGP), DB connection strings, .env dumps, JWTs and high-entropy strings. MCP server + pay

    ClaudeCursorCopilotGemini
    secret-scannerMIT3mo agonpmGitHubobserved · static extraction
    mcpmodel-context-protocolsecret-scannersecretssecurityapi-key
  4. tools.knurl/secret-scannerMCPcommunitydegradedtrust 60/100 · B
    v0.1.0

    Scan configs, files, or text for leaked secrets and obvious misconfigurations. Nothing stored.

    ClaudeCursorCopilotChatGPTGemini
    tools.knurlUnknown3mo agoobserved · live tools/list
    mcp

All indexed toolsSearch the registry for scan_for_secrets