GitHub Security Posture MCP server
AI 에이전트가 GitHub organization, repository, Actions workflow, secrets 및 access control의 보안 설정 오류를 감사할 수 있도록 지원합니다.
다른 이름 badchars/github-security-mcp
- 스타
- 15
- Tools
- 39
- 다운로드, 30일
- 978
- 최신 버전
- —
- 마지막 커밋
- 2026년 3월 14일
- 라이선스
- MIT
GitHub Security Posture MCP란?
GitHub Security Posture은(는) MCP server입니다. AI 에이전트가 GitHub organization, repository, Actions workflow, secrets 및 access control의 보안 설정 오류를 감사할 수 있도록 지원합니다. 39개 도구를 제공합니다. 예: github_check_org_security, github_check_org_sso, github_check_org_members.
프로젝트 README에서 생성된 요약
GitHub Security Posture MCP server 정보
이 MCP server는 AI 에이전트가 GitHub organization과 repository의 보안 설정 오류를 감사할 수 있도록 지원합니다. AI가 organization 설정, repository 구성, GitHub Actions workflow, secret scanning 상태 및 access control 권한을 검사할 수 있는 통합된 방법을 제공합니다. 개발자는 여러 대시보드를 수동으로 클릭하는 대신 Claude Desktop 또는 Cursor와 같은 AI 클라이언트를 사용하여 포괄적인 보안 태세 분석을 수행할 수 있습니다.
이 server는 Model Context Protocol을 사용하여 6가지 카테고리에 걸쳐 39개의 특정 도구와 45개의 보안 점검 항목을 제공합니다. 제공된 GitHub token(일반 Personal Access Token 또는 fine-grained PAT)을 사용하여 GitHub API를 직접 호출하는 방식으로 작동합니다. 기본적인 가시성을 확보하는 데 GitHub Enterprise 구독이 필수적이지 않도록 설계되었으며, supply chain 리스크, workflow 내 script injection, 오래된 협업자 권한 등을 파악할 수 있습니다.
활용 사례
- 1전체 organization 감사 수행AI 에이전트에게 전체 GitHub organization에 대한 완전한 보안 감사를 실행하도록 요청하여 중요한 취약점을 식별하고 우선순위를 지정하십시오.
- 2CI/CD workflow 보안 분석AI 에이전트가 unpinned actions 또는 위험한 pull_request_target 패턴과 같은 supply chain 리스크를 GitHub Actions workflow에서 스캔하도록 하십시오.
- 3repository access control 검토에이전트를 사용하여 과도한 권한을 가진 사용자나 여전히 write 권한을 보유한 오래된 외부 협업자를 식별하십시오.
- 4secret 노출 리스크 탐지AI에게 secret scanning이 활성화되어 있는지, organization secrets가 특정 repository에 적절히 범위가 지정되었는지 확인하도록 지시하십시오.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
GitHub Security Posture MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 GitHub Security Posture MCP 설치
$ claude mcp add github-security-mcp -- npx -y github-security-mcpCursor에 GitHub Security Posture MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"github-security-mcp": {
"command": "npx",
"args": [
"-y",
"github-security-mcp"
]
}
}
}VS Code에 GitHub Security Posture MCP 설치
.vscode/mcp.json
{
"servers": {
"github-security-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"github-security-mcp"
]
}
}
}VS Code CLI에 GitHub Security Posture MCP 설치
$ code --add-mcp '{"name":"github-security-mcp","type":"stdio","command":"npx","args":["-y","github-security-mcp"]}'Claude Desktop에 GitHub Security Posture MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"github-security-mcp": {
"command": "npx",
"args": [
"-y",
"github-security-mcp"
]
}
}
}Codex에 GitHub Security Posture MCP 설치
$ codex mcp add github-security-mcp -- npx -y github-security-mcpCodex config.toml에 GitHub Security Posture MCP 설치
~/.codex/config.toml
[mcp_servers.github-security-mcp] command = "npx" args = ["-y", "github-security-mcp"]
Gemini CLI에 GitHub Security Posture MCP 설치
$ gemini mcp add -s user github-security-mcp npx -- -y github-security-mcpGemini settings.json에 GitHub Security Posture MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"github-security-mcp": {
"command": "npx",
"args": [
"-y",
"github-security-mcp"
]
}
}
}GitHub Security Posture MCP 도구 39
README에서 감지됨github_check_org_securitygithub_check_org_ssogithub_check_org_membersgithub_check_org_appsgithub_check_org_webhooksgithub_check_org_audit_loggithub_list_org_reposgithub_check_repo_branch_protectiongithub_check_repo_secretsgithub_check_repo_code_scanninggithub_check_repo_dependabotgithub_check_repo_settings
| github_check_org_security | — | |
| github_check_org_sso | — | |
| github_check_org_members | — | |
| github_check_org_apps | — | |
| github_check_org_webhooks | — | |
| github_check_org_audit_log | — | |
| github_list_org_repos | — | |
| github_check_repo_branch_protection | — | |
| github_check_repo_secrets | — | |
| github_check_repo_code_scanning | — | |
| github_check_repo_dependabot | — | |
| github_check_repo_settings | — |
도구 39개 모두 보기도구 수 줄이기
github_check_repo_webhooksgithub_check_repo_deploy_keysgithub_check_repo_codeownersgithub_check_workflow_injectiongithub_check_workflow_pr_targetgithub_check_workflow_permissionsgithub_check_workflow_pinninggithub_check_workflow_runnersgithub_check_workflow_environmentsgithub_check_workflow_secretsgithub_check_workflow_oidcgithub_check_secret_scanninggithub_check_push_protectiongithub_check_secret_patternsgithub_check_secret_scopinggithub_check_dependency_graphgithub_check_dependabot_updatesgithub_check_sbomgithub_check_vulnerabilitiesgithub_check_team_permissionsgithub_check_collaboratorsgithub_check_app_permissionsgithub_check_pat_usagegithub_list_checksgithub_audit_summarygithub_audit_reportgithub_run_all
| github_check_repo_webhooks | — | |
| github_check_repo_deploy_keys | — | |
| github_check_repo_codeowners | — | |
| github_check_workflow_injection | — | |
| github_check_workflow_pr_target | — | |
| github_check_workflow_permissions | — | |
| github_check_workflow_pinning | — | |
| github_check_workflow_runners | — | |
| github_check_workflow_environments | — | |
| github_check_workflow_secrets | — | |
| github_check_workflow_oidc | — | |
| github_check_secret_scanning | — | |
| github_check_push_protection | — | |
| github_check_secret_patterns | — | |
| github_check_secret_scoping | — | |
| github_check_dependency_graph | — | |
| github_check_dependabot_updates | — | |
| github_check_sbom | — | |
| github_check_vulnerabilities | — | |
| github_check_team_permissions | — | |
| github_check_collaborators | — | |
| github_check_app_permissions | — | |
| github_check_pat_usage | — | |
| github_list_checks | — | |
| github_audit_summary | — | |
| github_audit_report | — | |
| github_run_all | — |
구성
GITHUB_TOKEN
| 이름 | 설명 | 유형 |
|---|---|---|
| GITHUB_TOKEN | — |
자동 검사
2026년 11월 14일에 실행됨전체 보고서 →아직 인증되지 않았습니다. 서버는 80점 이상의 점수, 심각한 결함 없음, 그리고 검사에 충분한 데이터를 갖추어야 합니다. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능badchars/github-security-mcp is public and reachablegithub.com/badchars/github-security-mcp ↗통과
- 패키지가 이 저장소를 소스로 명시github-security-mcp names badchars/github-security-mcp as sourcenpmjs.com/package/github-security-mcp ↗통과
- 빌드 출처(Sigstore 증명)No build attestation published for this release검사되지 않음
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-03-14github.com/badchars/github-security-mcp ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음No popular package one edit away from github-security-mcp통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
- 모델에 대한 숨겨진 지침 없음39 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨No tool named like delete, drop or exec통과
- 원격 엔드포인트가 MCP 핸드셰이크에 응답검사되지 않음
README
GitHub에서 보기The Problem
GitHub security is fragmented. You need separate tools for org settings, repo configurations, Actions workflow analysis, secret scanning, supply chain, and access control. No single tool covers it all, and none work with AI agents.
Traditional workflow:
manually check org settings → click through 15 pages
run github-advisory-db for each repo → one at a time
grep workflows for script injection → miss half the patterns
review collaborator access → spreadsheet hell
check secret scanning alerts → another dashboard
──────────────────────────────────────────
Total: hours of manual work per org
github-security-mcp gives your AI agent 39 tools and 45 security checks via the Model Context Protocol. The agent calls GitHub APIs directly, understands what it finds, and tells you exactly what to fix.
With github-security-mcp:
You: "Audit my GitHub org for security issues and prioritize the fixes"
Agent: → checks org settings (2FA, SSO, member privileges)
→ scans repos (branch protection, secret scanning, Dependabot)
→ analyzes workflows (script injection, unpinned actions, OIDC)
→ reviews access (teams, collaborators, PATs, GitHub Apps)
→ "12 critical, 8 high — here are the top 5 to fix now"
How It's Different
Existing tools focus on one slice of GitHub security. github-security-mcp covers the full stack and works with any AI agent.
| Tool | What it does | What it can't do |
|---|---|---|
| Allstar | Enforce repo settings via GitHub App | No Actions analysis, no secret scanning, no access audit |
| Scorecard | OpenSSF security score for repos | Single-repo focus, no org-level checks, no real-time interaction |
| Legitify | Org + repo policy enforcement | CLI output, no AI integration, limited Actions analysis |
| step-security/harden-runner | Runtime Actions security | Only Actions, no org/repo/access checks |
| GitGuardian | Secret detection in commits | SaaS only, no self-hosted, limited to secrets domain |
| Socket | Supply chain risk analysis | Package-focused, no org/Actions/access analysis |
All of these are excellent tools. github-security-mcp doesn't replace them — it fills the gap of giving an AI agent unified, interactive access across all GitHub security domains.
Quick Start
Install
git clone https://github.com/badchars/github-security-mcp.git
cd github-security-mcp
bun install
Set up authentication
# Classic PAT (requires: repo, admin:org, admin:org_hook, admin:repo_hook)
export GITHUB_TOKEN=ghp_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
# Fine-grained PAT (preferred — least privilege)
# Organization: Members (read), Administration (read)
# Repository: Administration, Code scanning, Dependabot, Secret scanning,
# Actions, Environments, Webhooks (all read-only)
Connect to your AI agent
claude mcp add github-security -- bun run /path/to/github-security-mcp/src/index.ts
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"github-security": {
"command": "bun",
"args": ["run", "/path/to/github-security-mcp/src/index.ts"],
"env": {
"GITHUB_TOKEN": "ghp_your_token_here"
}
}
}
}
Same JSON config format. Point the command to your installation path.
Start auditing
You: "Audit my GitHub org for security misconfigurations"
That's it. The agent handles the rest.
What The AI Can Do
Full Organization Audit
You: "Run a complete security audit on our GitHub org"
Agent: → github_run_all {org: "myorg", repo: "main-app"}
→ 45 checks across 6 categories
→ github_audit_report
→ "34 findings: 4 critical, 7 high, 12 medium.
Critical #1: No branch protection on main (REPO-001)
Critical #2: Script injection in deploy.yml (ACT-001)
Critical #3: 3 critical Dependabot alerts unfixed 90+ days (REPO-007)
Critical #4: Unresolved secret scanning alerts (SEC-002)
Here are the exact fixes for each..."
Actions Workflow Security
You: "Check our CI/CD workflows for supply chain risks"
Agent: → github_check_workflow_injection
Found ${{ github.event.issue.title }} in run: block (deploy.yml:47)
→ github_check_workflow_pinning
12 actions use tags instead of SHA pins
→ github_check_workflow_pr_target
build.yml uses pull_request_target with checkout — critical risk
→ github_check_workflow_permissions
Default GITHUB_TOKEN has write-all permissions
→ "4 supply chain risks found. The PR target + checkout pattern
allows any fork to execute arbitrary code with write access
to your repo. Fix this first."
Access Control Review
You: "Who has too much access to our repositories?"
Agent: → github_check_team_permissions
"platform" team has admin on 47 repos, only 3 members
→ github_check_collaborators
8 outside collaborators with write access
→ github_check_app_permissions
"old-ci-bot" GitHub App has admin + all repos
→ github_check_pat_usage
14 classic PATs with repo scope (should be fine-grained)
→ "Reduce blast radius: restrict platform team to maintain,
remove 3 stale outside collaborators, limit old-ci-bot
to specific repos, migrate classic PATs to fine-grained."
Secret Exposure Detection
You: "Are we properly protecting secrets across our repos?"
Agent: → github_check_secret_scanning
Secret scanning disabled on 5 private repos
→ github_check_push_protection
3 push protection bypasses in the last month
→ github_check_secret_patterns
No custom secret patterns defined
→ github_check_secret_scoping
2 org secrets available to all repos (should be scoped)
→ "Enable secret scanning on all repos, review the 3 bypasses,
add custom patterns for internal API keys, and scope
org secrets to only the repos that need them."
Tools Reference (39 tools)
| Tool | Description |
|---|---|
github_check_org_security |
2FA enforcement, default repo visibility, member creation privileges |
github_check_org_sso |
SSO/SAML configuration via GraphQL |
github_check_org_members |
Outside collaborators, stale member detection |
github_check_org_apps |
OAuth credential authorizations, GitHub App installation permissions |
github_check_org_webhooks |
Insecure webhook URLs (HTTP, no secret) |
github_check_org_audit_log |
Suspicious audit log activity (Enterprise) |
github_list_org_repos |
List all repos in an org with security metadata |
| Tool | Description |
|---|---|
github_check_repo_branch_protection |
Branch protection rules on default branch |
github_check_repo_secrets |
Secret scanning and push protection enablement |
github_check_repo_code_scanning |
CodeQL / code scanning enabled, open alerts |
github_check_repo_dependabot |
Dependabot enabled, critical alert triage |
github_check_repo_settings |
SECURITY.md, private vulnerability reporting, fork restrictions |
github_check_repo_webhooks |
Insecure repo-level webhook URLs |
github_check_repo_deploy_keys |
Deploy key permissions (read-only vs read-write) |
github_check_repo_codeowners |
CODEOWNERS file presence and enforcement |
| Tool | Description |
|---|---|
github_check_workflow_injection |
Script injection via ${{ github.event.* }} in run: blocks |
github_check_workflow_pr_target |
pull_request_target + checkout pattern (critical) |
github_check_workflow_permissions |
GITHUB_TOKEN default permission scope |
github_check_workflow_pinning |
Unpinned third-party actions (tag vs SHA) |
github_check_workflow_runners |
Self-hosted runner exposure |
github_check_workflow_environments |
Missing environment protection rules |
github_check_workflow_secrets |
Secret exfiltration patterns in workflows |
github_check_workflow_oidc |
OIDC subject claim customization |
| Tool | Description |
|---|---|
github_check_secret_scanning |
Coverage gaps and unresolved alerts |
github_check_push_protection |
Push protection bypass tracking |
github_check_secret_patterns |
Custom secret pattern configuration |
github_check_secret_scoping |
Environment, repo, and org-level secret scoping |
| Tool | Description |
|---|---|
github_check_dependency_graph |
Dependency graph enablement |
github_check_dependabot_updates |
Dependabot security updates configuration |
github_check_sbom |
SBOM generation capability |
github_check_vulnerabilities |
Known vulnerabilities, critical unfixed > 90 days |
| Tool | Description |
|---|---|
github_check_team_permissions |
Team permission levels across repos |
github_check_collaborators |
External collaborator access audit |
github_check_app_permissions |
GitHub App permission scope review |
github_check_pat_usage |
Classic vs fine-grained PAT usage |
| Tool | Description |
|---|---|
github_list_checks |
Browse all 45 checks, filter by category/severity |
github_audit_summary |
Aggregate findings by category, severity, status |
github_audit_report |
Full markdown or JSON audit report |
github_run_all |
Execute all checks for an org/repo |
Check Registry (45 checks)
| ID | Check | Severity |
|---|---|---|
| ORG-001 | 2FA not enforced | CRITICAL |
| ORG-002 | Default repo visibility is public | HIGH |
| ORG-003 | Members can create public repos | MEDIUM |
| ORG-004 | SSO/SAML not configured | HIGH |
| ORG-005 | Outside collaborators with access | MEDIUM |
| ORG-006 | Stale organization members | LOW |
| ORG-007 | Risky OAuth app authorizations | HIGH |
| ORG-008 | Over-permissive GitHub App installations | HIGH |
| ORG-009 | Insecure webhook URLs | MEDIUM |
| ORG-010 | Suspicious audit log activity | INFO |
| ID | Check | Severity |
|---|---|---|
| REPO-001 | Missing or weak branch protection | CRITICAL |
| REPO-002 | Secret scanning not enabled | HIGH |
| REPO-003 | Push protection not enabled | HIGH |
| REPO-004 | Code scanning not enabled | MEDIUM |
| REPO-005 | Open code scanning alerts | HIGH |
| REPO-006 | Dependabot not enabled | MEDIUM |
| REPO-007 | Critical Dependabot alerts | CRITICAL |
| REPO-008 | No SECURITY.md policy file | LOW |
| REPO-009 | Private vulnerability reporting off | LOW |
| REPO-010 | Unrestricted fork settings | LOW |
| REPO-011 | Insecure repo webhooks | MEDIUM |
| REPO-012 | Read-write deploy keys | HIGH |
| REPO-013 | Missing CODEOWNERS file | LOW |
| ID | Check | Severity |
|---|---|---|
| ACT-001 | Script injection via untrusted inputs | CRITICAL |
| ACT-002 | pull_request_target with checkout | CRITICAL |
| ACT-003 | Over-permissive GITHUB_TOKEN | HIGH |
| ACT-004 | Unpinned third-party actions | MEDIUM |
| ACT-005 | Self-hosted runner exposure | HIGH |
| ACT-006 | Missing environment protection rules | MEDIUM |
| ACT-007 | Secret exfiltration patterns | HIGH |
| ACT-008 | OIDC misconfiguration | MEDIUM |
| ID | Check | Severity |
|---|---|---|
| SEC-001 | Secret scanning coverage gaps | HIGH |
| SEC-002 | Unresolved secret scanning alerts | CRITICAL |
| SEC-003 | Push protection bypasses | HIGH |
| SEC-004 | No custom secret patterns | LOW |
| SEC-005 | Overly broad secret scoping | MEDIUM |
| ID | Check | Severity |
|---|---|---|
| SUP-001 | Dependency graph not enabled | MEDIUM |
| SUP-002 | Dependabot security updates off | HIGH |
| SUP-003 | No SBOM generation | LOW |
| SUP-004 | Critical known vulnerabilities | CRITICAL |
| SUP-005 | Stale unfixed vulnerabilities (>90 days) | HIGH |
| ID | Check | Severity |
|---|---|---|
| ACC-001 | Over-permissive team access | HIGH |
| ACC-002 | External collaborators with write+ | MEDIUM |
| ACC-003 | Over-scoped GitHub Apps | HIGH |
| ACC-004 | Classic PATs with broad scopes | HIGH |
Architecture
src/
├── index.ts Entry point + MCP stdio
├── types/
│ └── index.ts CheckResult, ToolDef, ToolContext, ToolResult
├── github/
│ └── client.ts GitHubClientFactory (lazy Octokit + GraphQL)
├── protocol/
│ ├── tools.ts 39 tool definitions (Zod schemas)
│ └── mcp-server.ts MCP server + stdio transport
├── org/ Organization checks (ORG-001..010)
│ ├── security.ts 2FA, visibility, member privileges
│ ├── sso.ts SSO/SAML via GraphQL
│ ├── members.ts Outside collaborators, stale members
│ ├── apps.ts OAuth apps, GitHub App installations
│ ├── webhooks.ts Insecure webhook URLs
│ └── audit-log.ts Suspicious audit log patterns
├── repo/ Repository checks (REPO-001..013)
│ ├── branch-protection.ts Branch protection rules
│ ├── secret-scanning.ts Secret scanning + push protection
│ ├── code-scanning.ts CodeQL enabled, open alerts
│ ├── dependabot.ts Dependabot enabled, critical alerts
│ ├── settings.ts SECURITY.md, vuln reporting, forks
│ ├── webhooks.ts Insecure repo webhooks
│ ├── deploy-keys.ts Deploy key permissions
│ └── codeowners.ts CODEOWNERS file
├── actions/ GitHub Actions checks (ACT-001..008)
│ ├── injection.ts Script injection via untrusted inputs
│ ├── pr-target.ts pull_request_target + checkout
│ ├── permissions.ts GITHUB_TOKEN default permissions
│ ├── pinning.ts Unpinned third-party actions
│ ├── runners.ts Self-hosted runner exposure
│ ├── environments.ts Environment protection rules
│ ├── secrets.ts Secret exfiltration patterns
│ └── oidc.ts OIDC configuration
├── secrets/ Secret management checks (SEC-001..005)
│ ├── scanning.ts Coverage + alert triage
│ ├── push-protection.ts Push protection bypasses
│ ├── patterns.ts Custom secret patterns
│ └── scoping.ts Env/repo/org secret scoping
├── supply-chain/ Supply chain checks (SUP-001..005)
│ ├── dependency-graph.ts Dependency graph enabled
│ ├── dependabot-updates.ts Security updates config
│ ├── sbom.ts SBOM generation
│ └── vulnerabilities.ts Known vulns, stale unfixed
├── access/ Access control checks (ACC-001..004)
│ ├── teams.ts Team permission audit
│ ├── collaborators.ts External collaborators
│ ├── github-apps.ts GitHub App permissions
│ └── tokens.ts Classic vs fine-grained PATs
└── meta/ Aggregation + reporting
├── list-checks.ts CHECK_REGISTRY (45 checks)
├── summary.ts Findings aggregation
├── report.ts Markdown/JSON report
└── run-all.ts Execute all checks
Design decisions:
- Single Octokit instance — GitHub API is global (no regions). Lazy initialization on first API call.
- Uniform CheckResult — Every check returns the same structure: checkId, severity, status, details, remediation. Same pattern as cloud-audit-mcp.
- Static workflow analysis — Actions checks fetch YAML via Contents API and use regex analysis. GitHub has no parsed workflow API.
- Enterprise graceful degradation — Enterprise-only features (audit log, credential authorizations, SSO) return
NOT_APPLICABLEinstead of errors. - In-memory findings — Session-scoped findings array. No database, no persistence. Run
github_audit_summaryorgithub_audit_reportto aggregate. - 4 dependencies —
@modelcontextprotocol/sdk,@octokit/rest,@octokit/graphql,zod. Nothing else.
Authentication
| Token Type | Required Scopes |
|---|---|
| Classic PAT | repo, admin:org, admin:org_hook, admin:repo_hook |
| Fine-grained PAT (recommended) | Org: Members + Administration (read). Repo: Administration, Code scanning, Dependabot, Secret scanning, Actions, Environments, Webhooks (read) |
| GitHub App | Same repository/org permissions as fine-grained PAT |
The token is read from the GITHUB_TOKEN environment variable.
Part of the MCP Security Suite
| Project | Domain | Tools |
|---|---|---|
| hackbrowser-mcp | Browser-based security testing | 39 tools, Firefox, injection testing |
| cloud-audit-mcp | Cloud security (AWS/Azure/GCP) | 38 tools, 60+ checks |
| github-security-mcp | GitHub security posture | 39 tools, 45 checks |
Limitations
- Requires a GitHub PAT or GitHub App token with appropriate scopes
- Some checks require GitHub Enterprise Cloud (audit log, credential authorizations, SSO) — these gracefully return NOT_APPLICABLE on free/Team plans
- Actions workflow analysis is regex-based (no AST parsing) — may miss complex injection patterns
- Rate limiting: GitHub API allows 5,000 requests/hour for authenticated users. A full org audit with many repos may approach this limit
- macOS / Linux (Windows not tested)
GitHub Security Posture MCP 질문
GitHub Security Posture MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add github-security-mcp -- npx -y github-security-mcp를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
GitHub Security Posture MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
GitHub Security Posture MCP는 어떤 도구를 제공하나요?
39개 도구를 제공합니다. 예: github_check_org_security, github_check_org_sso, github_check_org_members, github_check_org_apps, github_check_org_webhooks.
이 MCP server는 GitHub 보안과 관련하여 AI 에이전트에게 어떤 기능을 제공하나요?
에이전트에게 39개의 도구와 45개의 보안 점검 항목을 제공하여 organization 설정, repository, Actions workflow, secrets, supply chain 및 access control을 감사하고 우선순위가 지정된 수정 사항을 보고할 수 있게 합니다.
GitHub security MCP server 인증은 어떻게 하나요?
GITHUB_TOKEN 환경 변수를 설정하십시오. 일반 PAT 또는 organization 및 repository security scope를 가진 fine-grained read-only PAT를 사용할 수 있습니다.
GitHub Actions workflow의 supply chain 리스크를 분석할 수 있나요?
네, script injection, pull_request_target 오용, unpinned actions, token permissions, runners, environments, secrets, OIDC를 포함한 8가지 Actions 점검을 수행합니다.
이 점검을 실행하려면 GitHub Enterprise가 필요한가요?
아니요, public API를 사용하여 무료로 작동하며 Enterprise 전용 기능도 원활하게 처리합니다. 다만 organization audit log와 같은 일부 점검은 Enterprise가 필요합니다.
Claude Code에 어떻게 연결하나요?
bun을 사용하여 서버의 src/index.ts 엔트리 파일을 가리키는 claude mcp add 명령어를 실행하십시오.