Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-10 17:47 UTC

modelcontextprotocol / ruby-sdk

The official Ruby SDK for the Model Context Protocol servers and clients.

RubyCustom license★ 906 stars⑂ 133 forkssince Feb 2025View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

modelcontextprotocol/ruby-sdk holds a health index of 96 out of 100, placing it in the Exceptional band. It scores highest on Vitality (100/100) and lowest on AI Readiness (64/100). It was last updated today. A single contributor accounts for most of its recent work.

96
overall / 100
Exceptional

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.

96
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 84 is calibrated to 96 on the published index scale (record calibration 2026-08-02).

Ownership

Model Context ProtocolOrganization · verified domain
50,538 followers42 public repossince Sep 2024

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsmcp1.5.1-351 day ago

Metrics by category

Vitality

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

100Exceptional · 21% of overall

Development activity

100Exceptional
How it's scored
36/36Push recency — last push 0 days ago
36/36Commit cadence — 52/52 weeks with commits
18/18Commit volume — 688 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year688
human_commit_share1
days_since_last_push0
active_weeks_last_year52

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 35 releases published
36/36Release recency — latest release 1 days ago
27/27Release cadence — a release every ~7.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count35
latest_release_tagv1.5.1
releases_from_tagsno
days_since_latest_release1
mean_days_between_releases7.1
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?

82Excellent · 17% of overall
How it's scored
48/60Stars — 906 stars
17.7/25Forks — 133 forks
6.5/15Watchers — 16 watchers
Inputs used
forks133
stars906
watchers16
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

86Excellent
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes
How it's scored
72.6/80Total downloads — 9,772,671 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesmcp
dependents—
ecosystemsrubygems
total_downloads9,772,671
monthly_downloads—
unverified_packages_excluded—
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

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

76Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
5.2/22.5Commit distribution — top contributor authored 77% of commits
13.5/13.5Contributor breadth — 49 contributors
10/10OpenSSF Scorecard: Contributors — project has 30 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled49
top_contributor_share0.768
How it's scored
41.5/42Issue resolution — 99% of issues closed
28.9/30PR acceptance — 435/452 decided PRs merged
8.7/13Newcomer PR acceptance — 2/3 first-time contributors' PRs merged in 30d
9/15OpenSSF Scorecard: Code-Review — Found 9/15 approved changesets -- score normalized to 6
Inputs used
merged_prs435
open_issues1
closed_issues89
prs_merged_7d9
prs_decided_7d10
prs_merged_30d44
prs_decided_30d45
issue_closed_ratio0.989
closed_unmerged_prs17
first_time_authors_30d3
first_time_prs_merged_30d2
first_time_prs_decided_30d3
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
25/25Owner reach — 50,538 followers of modelcontextprotocol
15.8/25Track record — 42 public repos, account ~1 yr old
Inputs used
followers50,538
owner_typeOrganization
is_verifiedyes
owner_loginmodelcontextprotocol
public_repos42
account_age_days719

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on rubygems
35/35Publish recency — latest publish 1 days ago
20/20Version history — 35 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesmcp
ecosystemsrubygems
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
16/16Linter config — .rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 15 out of 15 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://ruby.sdk.modelcontextprotocol.io
10/10Repository description
10/10Topics — 4 topics
0/10Wiki
Inputs used
topicsruby, mcp, mcp-server, mcp-client
has_wikino
homepagehttps://ruby.sdk.modelcontextprotocol.io
docs_sitehttps://ruby.sdk.modelcontextprotocol.io
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

79Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
4.5/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 15 out of 15 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
4.5/7.5Code-Review — Found 9/15 approved changesets -- score normalized to 6
2.5/2.5Contributors — project has 30 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
6.8/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate7.4
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages1
unassessed_packages22
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 1 resolved dependencies against OSV. 22 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

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.

64Moderate · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 99 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.99
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes5,946
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .rubocop.yml
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Ruby without a type-check config
51.5/55Manageable file sizes — 10/155 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes258,951
source_files_sampled155
oversized_source_files10
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

906GitHub stars
49contributors
688commits, last 12 months
0days since last push
35releases
1bus factor
1open issues
RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 133 ⇿
0Stars
133Forks
34Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

025507510012515013092025-052026-012026-09
Major 1Minor 30Patch 3

Each point covers 2 days.

OpenSSF Scorecard 7.4 / 10
7.4aggregate

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-09-10 17:46 UTC

10Binary-Artifactsno binaries found in the repo
6Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests15 out of 15 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 9/15 approved changesets -- score normalized to 6
10Contributorsproject has 30 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 13
RegistryPackageVersion constraintManifest
RubyGemsrubocop-minitest>= 0.39.0Gemfile
RubyGemsrubocop-rake—Gemfile
RubyGemsrubocop-shopify>= 2.18Gemfile
RubyGemspuma>= 5.0.0Gemfile
RubyGemsrack-cors—Gemfile
RubyGemsrackup>= 2.1.0Gemfile
RubyGemsactivesupport—Gemfile
RubyGemsdebug—Gemfile
RubyGemsi18n!= 1.15.0Gemfile
RubyGemsrake~> 13.0Gemfile
RubyGemssorbet-static-and-runtime—Gemfile
RubyGemsyard~> 0.9Gemfile
RubyGemsyard-sorbet~> 0.9Gemfile
All dependencies 23

Full resolved dependency set from the GitHub dependency graph: 9 direct and 14 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
RubyGemsactivesupport—direct
RubyGemsi18n1.15.0direct
RubyGemspuma—direct
RubyGemsrack-cors—direct
RubyGemsrackup—direct
RubyGemsrake—direct
RubyGemsrubocop-minitest—direct
RubyGemsrubocop-rake—direct
RubyGemsyard—direct
RubyGemsbase64—indirect
RubyGemsbigdecimal—indirect
RubyGemscsv—indirect
RubyGemsevent_stream_parser—indirect
RubyGemsfaraday—indirect
RubyGemsgithub-pages—indirect
RubyGemsjson_schemer—indirect
RubyGemslogger—indirect
RubyGemsmcp—indirect
RubyGemsminitest—indirect
RubyGemsmocha—indirect
RubyGemsrails—indirect
RubyGemswebmock—indirect
RubyGemswebrick—indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 1 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 22 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

No known advisories affect the assessed dependencies.

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

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 statistics — RubyGems.