List Dependabot security alerts for a GitHub repository to identify and manage vulnerable dependencies. Supports filtering by state, severity, package, and ecosystem.
MIT
650,545 tools. Updated 2026-10-14 07:11
"Dependabot" matching MCP tools:
- Retrieve a specific Dependabot alert by number and repository to access security vulnerability details and remediation guidance.MIT
- Disable automated Dependabot security fixes for a repository to prevent automatic patching of vulnerabilities.-
- Configure the default repository access level for Dependabot across an organization. Assign permissions for Dependabot to access repositories by default.-
- Retrieve Dependabot security alerts for a repository, filterable by severity, state, package, and more.-
- Enables automated security fixes on a GitHub repository using Dependabot to address vulnerable dependencies.-
Matching MCP Servers
- AlicenseBqualityAmaintenanceSelf-hosted GitHub MCP server for PR, repo file, and Dependabot operations, supporting multiple MCP clients with personal access token auth.7MIT
- AlicenseAqualityAmaintenanceEnables AI assistants to monitor GitHub repository health by calculating health scores, fetching repository metadata, analyzing Dependabot alerts, checking CI/CD status, and retrieving code scanning alerts.8119 npm1MIT
- Retrieve Dependabot security alerts for an organization, with filters by severity, state, ecosystem, and more.-
- Update a Dependabot alert's status or details. Specify owner, repo, alert number, and request body.-
- Installs missing CI/CD, security, dependabot, or maintenance files from a starter into an existing repo. Default dry-run previews the file plan; set dry_run false to apply only necessary changes.MIT
- Install authentication, payment, storage, production, and DevOps plugins into a BackGen project. Each plugin injects source files, registers routes, and updates dependencies.MIT
- Run a comprehensive security scan on a repository using multiple parallel scanners to detect vulnerabilities, secrets, and dependency CVEs, and receive a deduplicated severity-ranked report.MIT
- Compare two package versions to receive a structured upgrade analysis: semver classification, breaking changes, security advisories, migration guides, and a recommendation.MIT
- Identifies vulnerable package dependencies in a GitHub repository by fetching Dependabot alerts. Returns severity, package name, and state for each alert.MIT
- Compare an installed @mushi-mushi/* package version against the published catalog to reveal SDK drift, then get actionable next steps (docs search or upgrade skill) when outdated.MIT
- Calculate a 0-100 health score and A-F grade for any GitHub repository, combining CI status, security, community, and maintenance data with actionable improvement tips.MIT
- Retrieve GitHub API metadata including IP ranges, SSH key fingerprints, public keys, and password auth status to support firewall allowlisting, SSH host verification, and infrastructure automation.MIT
- Batch-analyze up to 50 package upgrades to get a unified risk report ranked by security, caution, review, likely-safe, and safe, with breaking changes and CVEs.MIT
- Audit a GitHub repository against 12 open-source best practices to get a weighted 0-100 score, grade, and actionable fixes for missing items.MIT
- Summarize GitHub security alerts (code scanning, Dependabot, secret scanning) with severity breakdown and recommended fix order.MIT
- Audit a local repository for security CI hygiene, checking gitleaks, CodeQL, dependency audits, license compliance, Dependabot, and secret scanning. Ensures alignment with the Starter Series quality bar.MIT
- Retrieve Dependabot alerts for a repository, grouped by severity, to monitor open, fixed, or dismissed vulnerabilities.MIT