All teardowns
github logo

Free Verify scan · github/github-mcp-server

github-mcp-server scores 72/100

GitHub's official Model Context Protocol server.

Commit c59e8c1 · 132 controls · Oct 15, 2026 · Re-checked daily

Scanned with public access only. Customer results are never published.

Delivery controls score72
github-mcp-server
42median 6886

Out of 100. Stronger than 68% of the 68 other assessed repositories.

Score

72/100

Rank 20 of 69 · median 68

Gaps

30

3 fewer than the median of 33

Critical

3 controls

1 root cause

Not visible

15

Needs admin access

What github-mcp-server does wellDefault branch identifiedBranch strategy observableDefault branch protected by rulesetForce-push restrictedPull-request requirement on default branch
Gaps30
github-mcp-server
15median 3361

Visible controls Verify found unmet. Fewer is better. Stronger than 65% of the 68 other assessed repositories.

How does your team compare?

This is what Canon Verify found in github-mcp-server's public configuration. Your team's process probably has the same gaps. Most private repos do.

See how your team scores

5 minutes. No repository access needed.

Scan your own repo with Verify (free)

Analysis

Our read

01

Security leads the assessment.

13 of 14 visible controls pass in security.

02

Code quality has the most room to improve.

6 visible controls remain open in code quality.

Priority

Fix these first

critical

Production approvers named

Covers 3 controls
  • Production approvers named
  • Production protection
  • Production reviewers resolved

What Verify read

No resolved production reviewers.

Risk: Unnamed production approvers mean deployment approval falls to whoever is nearby when the button needs pressing.

text
Name production reviewers.

Have this gap too? Start from the PR Review Pipeline flow.

Open in Design
high

Workflow permissions least-privilege

Covers 1 control
  • Workflow permissions least-privilege

What Verify read

One or more workflows do not declare a permissions block.

Risk: Broadly permissioned workflows hand a write token to every action they call, including third-party code.

text
Set least-privilege GITHUB_TOKEN.
high

Default workflow token read-only

Covers 1 control
  • Default workflow token read-only

What Verify read

At least one workflow grants write permissions at the top level or declares none.

Risk: A write-by-default token lets any compromised action push code or publish a release.

text
Set default workflow permissions to read.

Overview

Control map

Public-access limit

15 controls this scan couldn't read

This free scan used public access only. These controls live in settings only a repository admin can read. Verify checks them on your connected repository.

  • Administrator bypass restrictedhigh
  • Tag protectionhigh
  • Self-merge restrictedhigh
  • Bypass actors justifiedhigh
  • Push protection enabledhigh
  • Dependabot alertshigh
  • Secret scanning alertshigh
  • SAST required on default branchhigh
  • Environment secrets scopedhigh
  • Secret custodiansmedium
  • Agent identity in commitsmedium
  • Audit of agent actionsmedium
  • Audit of privileged actionsmedium
  • Private vulnerability reportinglow
  • Wait timer or freeze windowlow
Get Verify

Method

How Verify works

01

Read

Verify reads the repository at a pinned commit: settings, rulesets, workflows, and files.

02

Judge

Each control is checked against a written expectation. Same inspector, same criteria, every repository.

03

Prove

Every result shows the evidence Verify read. Assessments re-run daily, and changes are logged.

132 controls · 69 repositories assessed · re-run daily

This free scanVerify on your repository
AccessPublicGitHub App you install
Controls read109 of 109All 109
Private repositoriesNoYes
ResultsPublished herePrivate to your organization

Evidence locker

Every control Verify checked

Governance

8 of 12 pass

Review

19 of 26 pass

CI & tests

23 of 30 pass

Code quality

2 of 8 pass

Security

13 of 20 pass

Agents & AI

5 of 8 pass

Release & ops

5 of 22 pass

Docs

4 of 6 pass

Assessment timeline

Canon re-assesses this repository daily. An entry appears only when something changed — the score, a control's outcome, or a control ceasing to apply.

Sep 21 · 70Oct 15 · 72
  • Oct 8, 2026Delivery controls score 70 → 7255edd58
  • Oct 8, 2026Reusable workflows or action pins · CI & tests — gap → confirmed55edd58
  • Oct 8, 2026Action SHA pins · Security — gap → confirmed55edd58
  • Oct 8, 2026No mutable tags for release artifacts · Security — gap → confirmed55edd58

Get this report for your own repository.

Canon Verify runs the same inspection on your private repo. Read-only GitHub App. First scan free.

Read-only access. No code stored. How Canon handles your data →

View github/github-mcp-server on GitHub

Maintain github-mcp-server? If anything here is inaccurate or out of date, email security@strikelabs.co and we'll correct it.