The Kensai MCP Suite turns the platform into a tool any LLM can call —
Claude, ChatGPT, Cursor, Copilot, your in-house agent. SARIF in, JSON
out. Findings, scans, hunts, governance, billing — all addressable.
{[
'GITHUB','GITLAB','BITBUCKET','JIRA','LINEAR','SLACK','PAGERDUTY','OPSGENIE',
'SPLUNK','DATADOG','SENTRY','ELASTIC','SUMOLOGIC','SNYK','SEMGREP','TRIVY',
'AWS','GCP','AZURE','CLOUDFLARE','VERCEL','FASTLY','OKTA','AUTH0',
'HACKERONE','BUGCROWD','INTIGRITI','YESWEHACK','CLAUDE','OPENAI','CURSOR','MCP',
].map(b => (
{b}
))}
MCP · /findings.list
"Hey Claude, what bled overnight?"
Your AppSec lead can ask plain-English questions of the platform. Kensai responds with structured findings, gates, and remediation steps — auditable, attributable, and never made up.
{`$ kensai mcp call findings.list \\
--tenant quanta-labs \\
--since '6h ago' \\
--severity '>=high'
`}{`# 4 findings · gate-verified
`}{`F-1824 `}CRITICAL{` G3 SQL injection · /api/users/login
F-1819 `}CRITICAL{` G3 RCE deserialization · /jobs/run
F-1823 `}HIGH {` G5 IDOR · /orgs/:id/billing
F-1822 `}HIGH {` G3 Path traversal · /files/:name
`}{`# evidence: oci://kensai-evidence/F-1824/poc.har
# autofix: PR #4421 opened · qlabs/api
# bounty: review path available when a finding is ready`}{`
`}● next: type 'forge F-1824' to advance to G4