GitHub Security Vuln Triage

Name: GitHub Security Vuln Triage
Availability: InStock
Author: Kata Team

Re-prioritizes GitHub Dependabot alerts by exploitability, files Jira tickets, alerts Slack

Works with

Claude (web & desktop)ChatGPT (Plus / Pro)CursorVS Code (Copilot)Claude CodeGemini CLIWindsurfClineContinueZedLM StudioGooseJetBrains AI AssistantWarpPostmanand more

Before you connect: what this agent would do

A preview derived from this agent’s definition — not a live run. Nothing runs and no key is sent until you connect. FindAgent runs it in an isolated sandbox on the hosted connection.

Credentials it will ask for (4)

GitHub Token· optional
Only ever sent to: api.github.com
Jira API Token· optional
Only ever sent to: *.atlassian.net
Slack Bot Token· optional
Only ever sent to: slack.com
Anthropic API Key· optional
Only ever sent to: api.anthropic.com

Safety rails that guard it

Every result is scanned for leaked secrets and prompt-injection before it reaches you — a check no agent can turn off.

How FindAgent keeps agents safe

Connect over MCP — runs anywhere

GitHub Security Vuln Triage runs on FindAgent and connects over MCP — no download, no local runtime. Add the server URL to any MCP-capable client.

1 · Choose your client

1Find an agent

GitHub Security Vuln Triage

Free

Re-prioritizes GitHub Dependabot alerts by exploitability, files Jira tickets, alerts Slack

githubdependabot

ConnectConnecting…Connected

Add your credentials

GitHub Token· optional

••••••••••••

Jira API Token· optional

••••••••••••

Encrypted · only sent to api.github.com

Saved securely

chatgpt.com

ChatGPT

Run the full vulnerability triage across our repos and post…

FindAgent · GitHub Security Vuln Triage

✻ Spelunking…

FindAgent

Connected in ChatGPT

010203

2 · Add the server URL

remote MCP

https://mcp.findagent.cloud/agents/github-security-vuln-triage

ChatGPT (Plus / Pro): Settings → Connectors → add a remote MCP server, then paste the URL and approve it.

Open ChatGPT connectors

You add this server inside your client and approve it once — that in-client step is a security check, so there's no one-click button for it.

Signing in: the first time you connect, your client opens a FindAgent sign-in page — approve once and you're connected. There's no API key or token to copy; access is tied to your FindAgent account.

What you'll need — and where to get it

You enter these when you connect. They're encrypted, only ever sent to the agent's allowed hosts, and never shared with the creator.

GitHub Token · optional
GitHub personal access token or GitHub App token with security_events:read and repo:read scopes. Required for live Dependabot alert fetching; mock fixtures used without it.Create a personal access token in GitHub (Settings → Developer settings → Personal access tokens) scoped to what the agent needs.Paste the value as a single line.Only sent to: api.github.com
Jira API Token · optional
Jira API token (with your Atlassian account email) used to create triage tickets for critical/high vulnerabilities.Get this from *.atlassian.net's account or API settings.Paste the value as a single line.Only sent to: *.atlassian.net
Slack Bot Token · optional
Slack bot OAuth token (xoxb-...) with chat:write scope for posting the daily vulnerability triage summary.Create a Slack app (api.slack.com/apps), add the scopes the agent needs, install it to your workspace, and copy the bot/user token.Paste the value as a single line.Only sent to: slack.com
Anthropic API Key · optional
Optional. Leave blank on a sampling-capable client to use the host model with no key.Create a key on the Anthropic Console API keys page (console.anthropic.com → API keys).Paste the value as a single line.Only sent to: api.anthropic.com