Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-05 21:05 UTC

modelcontextprotocol / php-sdk

The official PHP SDK for Model Context Protocol servers and clients. Maintained in collaboration with The PHP Foundation.

PHPCustom license★ 1,601 stars⑂ 169 forkssince Jul 2025View on GitHub ↗

modelcontextprotocol/php-sdk holds a health index of 96 out of 100, placing it in the Exceptional band. It scores highest on Vitality (97/100) and lowest on AI Readiness (70/100). It was last updated today. 2 contributors account 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 83 is calibrated to 96 on the published index scale (record calibration 2026-08-02).

Ownership

Model Context ProtocolOrganization · verified domain
50,408 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
Packagistmcp/sdkv0.8.1870,827126 days ago

Metrics by category

Vitality

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

97Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
31.2/36Commit cadence — 45/52 weeks with commits
18/18Commit volume — 263 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 22 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year263
human_commit_share0.95
days_since_last_push0
active_weeks_last_year45

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 12 releases published
36/36Release recency — latest release 6 days ago
27/27Release cadence — a release every ~27.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count12
latest_release_tagv0.8.1
releases_from_tagsno
days_since_latest_release6
mean_days_between_releases27.3
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?

84Excellent · 17% of overall
How it's scored
52/60Stars — 1,601 stars
18.5/25Forks — 169 forks
7.6/15Watchers — 24 watchers
Inputs used
forks169
stars1,601
watchers24
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_badges8
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes
How it's scored
79.2/80Monthly downloads — 870,827 downloads/month across packagist
13/20Registry dependents — 88 packages depend on it
Inputs used
packagesmcp/sdk
dependents88
ecosystemspackagist
total_downloads3,210,592
monthly_downloads870,827
unverified_packages_excluded—

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
25.2/54Bus factor — 2 contributor(s) cover half of all commits
12/22.5Commit distribution — top contributor authored 46% of commits
13.5/13.5Contributor breadth — 49 contributors
10/10OpenSSF Scorecard: Contributors — project has 42 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled49
top_contributor_share0.465
How it's scored
27.3/42Issue resolution — 65% of issues closed
25.9/30PR acceptance — 279/323 decided PRs merged
4.3/13Newcomer PR acceptance — 3/9 first-time contributors' PRs merged in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 3/29 approved changesets -- score normalized to 1
Inputs used
merged_prs279
open_issues55
closed_issues102
prs_merged_7d7
prs_decided_7d9
prs_merged_30d52
prs_decided_30d59
issue_closed_ratio0.65
closed_unmerged_prs44
first_time_authors_30d7
first_time_prs_merged_30d3
first_time_prs_decided_30d9
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
25/25Owner reach — 50,408 followers of modelcontextprotocol
15.8/25Track record — 42 public repos, account ~1 yr old
Inputs used
followers50,408
owner_typeOrganization
is_verifiedyes
owner_loginmodelcontextprotocol
public_repos42
account_age_days715

Package maintenance

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

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 — .php-cs-fixer.dist.php
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 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://php.sdk.modelcontextprotocol.io
10/10Repository description
10/10Topics — 4 topics
0/10Wiki
Inputs used
topicsphp, mcp, mcp-server, mcp-client
has_wikino
homepagehttps://php.sdk.modelcontextprotocol.io
docs_sitehttps://php.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?

74Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 30 out of 30 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
0.8/7.5Code-Review — Found 3/29 approved changesets -- score normalized to 1
2.5/2.5Contributors — project has 42 contributing companies or organizations
0/10Dangerous-Workflow — no data
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 22 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0.5/5SAST — SAST tool is not run on all commits -- score normalized to 1
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate6.8
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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_packages33
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. 33 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.

70Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 92 of 95 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.968
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
11/11Lint / format config — .php-cs-fixer.dist.php
0/11Static type checking
10/10Reproducible environment — Dockerfile
10/10Demonstrated agent practice — 10 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 5 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.1
toolchain_manifests—
dependency_bot_commit_share0.05
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — PHP without a type-check config
54.9/55Manageable file sizes — 1/572 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes64,219
source_files_sampled572
oversized_source_files1
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

1,601GitHub stars
49contributors
263commits, last 12 months
0days since last push
12releases
2bus factor
55open issues
Packagist, PyPIpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 169 ⇿
0Stars
169Forks
12Releases

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.

04080120160200169162025-092026-032026-09
Major 0Minor 8Patch 4
OpenSSF Scorecard 6.8 / 10
6.8aggregate

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-05 21:05 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 3/29 approved changesets -- score normalized to 1
10Contributorsproject has 42 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 22 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
1SASTSAST tool is not run on all commits -- score normalized to 1
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 12
RegistryPackageVersion constraintManifest
Packagistopis/json-schema^2.4composer.json
Packagistpsr/clock^1.0composer.json
Packagistpsr/container^1.0 || ^2.0composer.json
Packagistpsr/event-dispatcher^1.0composer.json
Packagistpsr/http-client^1.0composer.json
Packagistpsr/http-factory^1.1composer.json
Packagistpsr/http-message^1.1 || ^2.0composer.json
Packagistpsr/http-server-handler^1.0composer.json
Packagistpsr/http-server-middleware^1.0composer.json
Packagistpsr/log^1.0 || ^2.0 || ^3.0composer.json
Packagistsymfony/deprecation-contracts^2.5 || ^3.0composer.json
Packagistsymfony/uid^5.4 || ^6.4 || ^7.3 || ^8.0composer.json
All dependencies 34

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

RegistryPackageVersionRelation
Packagistopis/json-schema—direct
Packagistpsr/clock—direct
Packagistpsr/container—direct
Packagistpsr/event-dispatcher—direct
Packagistpsr/http-client—direct
Packagistpsr/http-factory—direct
Packagistpsr/http-message—direct
Packagistpsr/http-server-handler—direct
Packagistpsr/http-server-middleware—direct
Packagistpsr/log—direct
Packagistsymfony/deprecation-contracts—direct
Packagistsymfony/uid—direct
Packagistcomposer/semver—indirect
Packagistext-fileinfo—indirect
Packagistext-openssl—indirect
Packagistfirebase/php-jwt—indirect
Packagistlaminas/laminas-httphandlerrunner—indirect
Packagistnyholm/psr7—indirect
Packagistnyholm/psr7-server—indirect
Packagistphar-io/composer-distributor—indirect
Packagistphp—indirect
Packagistphp-cs-fixer/shim—indirect
Packagistphp-http/discovery—indirect
Packagistphpdocumentor/reflection-docblock—indirect
Packagistphpdocumentor/shim—indirect
Packagistphpstan/phpstan—indirect
Packagistphpunit/phpunit—indirect
Packagistpsr/simple-cache—indirect
Packagistsymfony/cache—indirect
Packagistsymfony/console—indirect
Packagistsymfony/finder—indirect
Packagistsymfony/http-client—indirect
Packagistsymfony/process—indirect
PyPIzensical0.0.50indirect
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. 33 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 — Packagist.