Skip to main content
Glama
rajbos

GHAS MCP server (GitHub Advanced Security)

by rajbos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to GHAS MCP server (GitHub Advanced Security)

No user-submitted related servers found.

    Related Servers

    • CVE Search MCP Server

      Arnabdaz
      F
      license
      A
      quality
      D
      maintenance
      Enables searching and analyzing CVEs and vulnerabilities from multiple sources, optimized for PR review scenarios to help developers identify the latest security issues.
      8
      2
      -

    • mcp-github-project-manager

      kunwarVivek
      A
      license
      C
      quality
      C
      maintenance
      Provides comprehensive tools for managing GitHub projects, milestones, tasks, and sprints. This server integrates deeply with GitHub Projects V2, offering features like automated kanban workflows, sprint planning, and custom field management.
      84
      26 npm
      100
      MIT

    • leak-secure-mcp

      cbuntingde
      A
      license
      A
      quality
      Not graded
      maintenance
      Enterprise-grade MCP (Model Context Protocol) server for detecting secrets and sensitive information in GitHub repositories. Scans for 35+ types of secrets including API keys, passwords, tokens, and credentials with production-ready reliability features.
      5
      0
      -
    • repo-doctor by Infojitsu

      repo-doctorofficial

      Infojitsu
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that produces scored, evidence-cited audits of public GitHub repos via tools for fetching metadata, reading files, scanning git history, and checking hygiene.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting different types of GitHub Advanced Security alerts: code scanning, Dependabot, and secret scanning. The descriptions explicitly differentiate the alert types, leaving no ambiguity about which tool to use for each security domain.

    Naming Consistency5/5

    All tools follow a perfect verb_noun pattern with 'list_' prefix followed by the specific alert type (code_scanning_alerts, dependabot_alerts, secret_scanning_alerts). The naming is completely consistent across all three tools with no deviations in style or structure.

    Tool Count3/5

    With only 3 tools, the server feels quite thin for GitHub Advanced Security's scope, which includes multiple security domains and potential operations beyond just listing alerts. While the tools cover the core alert types, the count is borderline minimal for what could be a more comprehensive security management interface.

    Completeness2/5

    The toolset is severely incomplete for GitHub Advanced Security operations. While it covers listing three types of alerts, there are significant gaps: no ability to create, update, dismiss, or resolve alerts; no access to security overviews or metrics; and no coverage of other GHAS features like code scanning analyses or security advisories. This creates dead ends for agents needing to take action on security findings.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources