Security Report

GitHub API MCP Security Report

Independent security and governance assessment · Assessed June 22, 2026 · Last updated June 26, 2026 · Verified 2×

Security

Compliance

MCPForge Score

Security Findings

Security

+Server reachable and responding

+Authentication flow detected

−4 destructive operations detected

−Credentials Vault not configured — API keys may be exposed through direct agent access if tools require authentication

Compliance

−User/contact data handling detected (GDPR/CCPA obligations)

−Deletion operations detected (GDPR Art. 17 audit trail required)

−Credentials Vault not configured — configure to ensure proper server-side key management

Risk Analysis

1191 tools analyzed

High Risk753

Medium Risk213

Low Risk225

By Category

Delete93

Billing43

Auth673

Admin66

Write91

○No approval workflows configured

Governance Assessment

Formal Security Review

✓ Approved

Completed June 22, 2026

Credentials Vault✗ Not Configured

Endpoint ProtectionNot Enabled

Audit Logging✓ Active — All tool invocations logged

Production Readiness

Enterprise Ready

MCPForge Score

→Configure the Credentials Vault to protect API keys from direct agent exposure.

→Enable endpoint protection to require API key authentication on direct MCP calls.

→Review the 753 high-risk tools and configure approval workflows where appropriate.

Related Guides

GitHub MCP: Setup, Security, Tools and Production Guide

Guide

Same Product

Best MCP Servers for Claude Code

Guide

Same Product

Related Templates

Express MCP Server with OAuth 2.0

Template

Same Product

Verix API MCP Server Starter

Template

Same Product

Related Verification

GitHub MCP