Secret Scan

Scan code, config or logs for leaked secrets: AWS keys, GitHub tokens, Stripe keys, API keys, private keys, database URLs and JWTs.

Pay by wallet (x402) secret-scan

Example

Example answer
{
  "clean": true,
  "findings": [],
  "lines_scanned": 1,
  "total_findings": 0,
  "severity_summary": {
    "high": 0,
    "medium": 0,
    "critical": 0
  }
}

Inputs

FieldTypeRequiredWhat it is
textstringYesCode, config, or log output

Output fields

How reliably each field appears in a successful answer.

FieldTypeAppears
cleanbooleanAlways (present in every successful answer)
findingsarrayAlways (present in every successful answer)
total_findingsintegerAlways (present in every successful answer)
severity_summaryobjectAlways (present in every successful answer)

How to call it

The same tool through each route. MCP clients reach it through Strale’s server at https://api.strale.io/mcp; the call below is what the agent sends.

# Needs an API key. max_price_cents caps what this call may cost.
curl -X POST https://api.strale.io/v1/do \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "capability_slug": "secret-scan",
    "inputs": {
      "text": "This is a test input for automated capability testing."
    },
    "max_price_cents": 2
  }'

Limitations

  • Custom formats and encrypted secrets are not detected

    Pattern-based detection of common secret formats — custom API key formats and encrypted secrets will not be detected

    What to do instead: Add custom regex patterns for your organisation's API key formats and service-specific credential patterns

Bundled checks that include it