Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-28 12:29 UTC

RedOrangeSweater / Meta.Tools.GithubMcp

GitHub's official MCP Server

GoMIT★ 0 stars⑂ 0 forkssince Jan 2026forkView on GitHub ↗
KindMCP serverCommand-line toolhow this is determined

RedOrangeSweater/Meta.Tools.GithubMcp holds a health index of 45 out of 100, placing it in the Weak band. It scores highest on AI Readiness (85/100) and lowest on Community & Adoption (12/100). It was last updated 236 days ago. 6 contributors account for most of its recent work.

45
overall / 100
Weak

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

45
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 47 is calibrated to 45 on the published index scale (record calibration 2026-08-02).

Ownership

RedOrangeSweaterOrganization
0 followers7 public repossince May 2020

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gogithub.com/github/github-mcp-serverpoints to another repo — not scoredv1.11.0-792 days ago

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

47Weak · 21% of overall
How it's scored
3.6/36Push recencylast push 236 days ago
13.2/36Commit cadence19/52 weeks with commits
18/18Commit volume207 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year207
human_commit_share0.71
days_since_last_push236
active_weeks_last_year19
How it's scored
16.2/27Ships releases47 version tags (no GitHub releases)
16.2/36Release recencylatest release 252 days ago
27/27Release cadencea release every ~2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count47
latest_release_tagv0.26.3
releases_from_tagsyes
days_since_latest_release252
mean_days_between_releases2
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

12Critical · 17% of overall
How it's scored
0/60Stars0 stars
0/25Forks0 forks
0/15Watchers0 watchers
Inputs used
forks0
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeno
has_licenseno
readme_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgoreportcard.com, shields.io
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

60Moderate · 23% of overall
How it's scored
48.6/54Bus factor6 contributor(s) cover half of all commits
18.5/22.5Commit distributiontop contributor authored 18% of commits
13.5/13.5Contributor breadth97 contributors
10/10OpenSSF Scorecard: Contributorsproject has 9 contributing companies or organizations
Inputs used
bus_factor6
contributors_sampled97
top_contributor_share0.179
How it's scored
0/42Issue resolution0% of issues closed
30/30PR acceptance3/3 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs3
open_issues1
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
0/25Owner reach0 followers of RedOrangeSweater
18.6/25Track record7 public repos, account ~6 yr old
Inputs used
followers0
owner_typeOrganization
is_verifiedno
owner_loginRedOrangeSweater
public_repos7
account_age_days2,289

Engineering Quality

Are baseline engineering and documentation practices in place?

56Moderate · 19% of overall
How it's scored
24/24CI workflows12 workflow(s)
24/24Tests present
16/16Linter config.golangci.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
6/20OpenSSF Scorecard: CI-Tests1 out of 3 merged PRs checked by a CI test -- score normalized to 3
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
0/30README
25/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_site
has_readmeno
has_docs_diryes
has_descriptionno

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

46Weak · 16% of overall
How it's scored
6/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0.8/2.5CI-Tests1 out of 3 merged PRs checked by a CI test -- score normalized to 3
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 9 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
5/5Packagingpackaging workflow detected
2/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
3.5/5SASTSAST tool detected but not run on all commits
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities16 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.6
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

85Excellent · 4% of overall
How it's scored
45/45Agent instructions.github/copilot-instructions.md
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://code.visualstudio.com/llms.txt)
40/40Legible commit history60 of 71 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://code.visualstudio.com/llms.txt
legible_history_share0.845
agent_instruction_files.github/copilot-instructions.md
agent_instruction_max_bytes13,137
How it's scored
12.6/18One-command bootstrapgo.mod (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format config.golangci.yml
11/11Static type checkingGo (statically typed)
10/10Reproducible environmentDockerfile, lockfile
10/10Demonstrated agent practice20 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance8 of the last 100 commits are automated dependency updates
4/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileyes
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.2
toolchain_manifestsgo.mod
dependency_bot_commit_share0.08
How it's scored
45/45Type-checkable codeGo (statically typed)
49.8/55Manageable file sizes9/95 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes116,635
source_files_sampled95
oversized_source_files9
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs
has_mcp_signalyes
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto). Remaining weights renormalized.

Key facts

0GitHub stars
97contributors
207commits, last 12 months
236days since last push
47releases
6bus factor
1open issues
Gopackage ecosystems

Data collection warnings

  • Community profile unavailable
  • go package 'github.com/github/github-mcp-server' points at a different repository (https://github.com/github/github-mcp-server); excluded from ecosystem scoring
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 4.6 / 10
4.6aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-08-28 12:28 UTC

8Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
3CI-Tests1 out of 3 merged PRs checked by a CI test -- score normalized to 3
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 9 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
10Packagingpackaging workflow detected
4Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
7SASTSAST tool detected but not run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities16 existing vulnerabilities detected
Direct dependencies 15
RegistryPackageVersion constraintManifest
Gogithub.com/google/go-github/v79v79.0.0go.mod
Gogithub.com/google/jsonschema-gov0.4.2go.mod
Gogithub.com/josephburnett/jdv1.9.2go.mod
Gogithub.com/microcosm-cc/bluemondayv1.0.27go.mod
Gogithub.com/migueleliasweb/go-github-mockv1.3.0go.mod
Gogithub.com/muesli/cache2gov0.0.0-20221011235721-518229cd8021go.mod
Gogithub.com/spf13/cobrav1.10.2go.mod
Gogithub.com/spf13/viperv1.21.0go.mod
Gogithub.com/stretchr/testifyv1.11.1go.mod
Gogithub.com/go-viper/mapstructure/v2v2.4.0go.mod
Gogithub.com/modelcontextprotocol/go-sdkv1.2.0go.mod
Gogithub.com/shurcooL/githubv4v0.0.0-20240727222349-48295856cce7go.mod
Gogithub.com/shurcooL/graphqlv0.0.0-20230722043721-ed46e5a46466go.mod
Gogithub.com/spf13/pflagv1.0.10go.mod
Gogithub.com/yosida95/uritemplate/v3v3.0.2go.mod
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsGo.