Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-16 04:07 UTC

KittyCAD / mcp

An MCP server housing various Zoo built utilities

PythonMIT★ 9 stars⑂ 1 forksince Sep 2025View on GitHub ↗
KindCommand-line toolMCP serverLibraryhow this is determined

KittyCAD/mcp holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Vitality (95/100) and lowest on Community & Adoption (39/100). It was last updated today. A single contributor accounts for most of its recent work.

86
overall / 100
Excellent

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.

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

Ownership

ZooOrganization · verified domain
920 followers88 public repossince Apr 2021

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIzoo_mcp0.27.05,642810 days agozoomcpkittycad3dmodelingserver

Metrics by category

Vitality

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

95Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
34.6/36Commit cadence — 50/52 weeks with commits
18/18Commit volume — 210 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year210
human_commit_share0.4
days_since_last_push0
active_weeks_last_year50
How it's scored
27/27Ships releases — 81 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~2.1 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count81
latest_release_tagv0.27.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases2.1

Community & Adoption

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

39Weak · 17% of overall
How it's scored
14.6/60Stars — 9 stars
0/25Forks — 1 forks
0/15Watchers — 1 watchers
Inputs used
forks1
stars9
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
50/80Monthly downloads — 5,642 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageszoo_mcp
dependents—
ecosystemspypi
total_downloads—
monthly_downloads5,642
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?

77Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
6.2/22.5Commit distribution — top contributor authored 73% of commits
13.5/13.5Contributor breadth — 11 contributors
10/10OpenSSF Scorecard: Contributors — project has 9 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled11
top_contributor_share0.726
How it's scored
30/42Issue resolution — 71% of issues closed
29.1/30PR acceptance — 222/229 decided PRs merged
11.4/13Newcomer PR acceptance — 7/8 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs222
open_issues10
closed_issues25
prs_merged_7d3
prs_decided_7d3
prs_merged_30d16
prs_decided_30d17
issue_closed_ratio0.714
closed_unmerged_prs7
first_time_authors_30d3
first_time_prs_merged_30d7
first_time_prs_decided_30d8
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
21.3/25Owner reach — 920 followers of KittyCAD
23.9/25Track record — 88 public repos, account ~5 yr old
Inputs used
followers920
owner_typeOrganization
is_verifiedyes
owner_loginKittyCAD
public_repos88
account_age_days1,993

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

66Good · 19% of overall
How it's scored
24/24CI workflows — 7 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff])
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
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
docs_site—
has_readmeyes
has_docs_dirno
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
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
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 9 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.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 3 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
5/5SAST — SAST tool is run on all commits
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
5.2/7.5Vulnerabilities — 3 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate7.4
Excluded from scoring (no data or not applicable): Packaging. 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
advisories6
affected_packages1
assessed_packages68
unassessed_packages0
affected_by_severityhigh 1
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 68 resolved dependencies against OSV. 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.

65Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://modelcontextprotocol.io/llms.txt)
40/40Legible commit history — 40 of 40 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://modelcontextprotocol.io/llms.txt
legible_history_share1
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes8,724
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
0/11Static type checking
10/10Reproducible environment — lockfile
6/10Demonstrated agent practice — 3 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 59 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.03
toolchain_manifests—
dependency_bot_commit_share0.59
How it's scored
0/45Type-checkable code — Python without a type-check config
47.8/55Manageable file sizes — 3/23 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes104,749
source_files_sampled23
oversized_source_files3
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

9GitHub stars
11contributors
210commits, last 12 months
0days since last push
81releases
1bus factor
10open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • pypi download statistics for 'zoo_mcp' unavailable this scan (stats endpoint failed after retries); adoption may be under-evidenced
  • pypi download figures for zoo_mcp carried forward from the previous scan (stats endpoint unavailable this scan)
  • deps.dev does not index pypi:zoo_mcp@0.27.0; advisories assessed against the repository dependency graph instead

More detail

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-16 04:07 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
10Code-Reviewall changesets reviewed
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
10Maintained30 commit(s) and 3 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
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
7Vulnerabilities3 existing vulnerabilities detected
Direct dependencies 11
RegistryPackageVersion constraintManifest
PyPIaiofiles<26.0pyproject.toml
PyPIhttpx>=0.28,<1pyproject.toml
PyPIkittycad>=1.5.0,<2.0pyproject.toml
PyPImcp>=2.2.0,<3pyproject.toml
PyPIpillow<13.0pyproject.toml
PyPIpymongo>=4.6.0,<5.0pyproject.toml
PyPItrimesh<6.0pyproject.toml
PyPItruststore<1.0pyproject.toml
PyPItyping-extensions>=4.12pyproject.toml
PyPIwebsockets>=14.1,<17.0pyproject.toml
PyPIzoo-kcl>=0.3.184pyproject.toml
All dependencies 68

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

RegistryPackageVersionRelation
PyPIaiofiles25.1.0direct
PyPIhttpx0.28.1direct
PyPIkittycad1.5.0direct
PyPImcp2.2.0direct
PyPIpillow12.3.0direct
PyPIpymongo4.18.0direct
PyPItrimesh5.1.0direct
PyPItruststore0.10.4direct
PyPItyping-extensions4.16.0direct
PyPIwebsockets16.0direct
PyPIzoo-kcl0.3.184direct
PyPIannotated-doc0.0.4indirect
PyPIannotated-types0.7.0indirect
PyPIanyio4.13.0indirect
PyPIattrs25.4.0indirect
PyPIcertifi2026.4.22indirect
PyPIcffi2.0.0indirect
PyPIclick8.3.3indirect
PyPIcolorama0.4.6indirect
PyPIcryptography48.0.1indirect
PyPIdnspython2.8.0indirect
PyPIexecnet2.1.2indirect
PyPIh110.16.0indirect
PyPIhttpcore1.0.9indirect
PyPIhttpcore22.13.0indirect
PyPIhttpx22.13.0indirect
PyPIhttpx2-jsfetch1.0indirect
PyPIidna3.19indirect
PyPIiniconfig2.3.0indirect
PyPIjsonschema4.26.0indirect
PyPIjsonschema-specifications2025.9.1indirect
PyPImarkdown-it-py4.2.0indirect
PyPImcp-types2.2.0indirect
PyPImdurl0.1.2indirect
PyPInumpy2.4.4indirect
PyPIopentelemetry-api1.44.0indirect
PyPIpackaging26.2indirect
PyPIphonenumbers9.0.30indirect
PyPIpluggy1.6.0indirect
PyPIpycparser3.0indirect
PyPIpydantic2.13.4indirect
PyPIpydantic-core2.46.4indirect
PyPIpydantic-extra-types2.11.1indirect
PyPIpygments2.20.0indirect
PyPIpyjwt2.13.0indirect
PyPIpytest9.0.3indirect
PyPIpytest-asyncio1.4.0indirect
PyPIpytest-httpx0.36.2indirect
PyPIpytest-rerunfailures16.6.1indirect
PyPIpytest-xdist3.8.0indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpython-dotenv1.2.2indirect
PyPIpython-multipart0.0.31indirect
PyPIpywin32311indirect
PyPIreferencing0.37.0indirect
PyPIrich15.0.0indirect
PyPIrpds-py0.30.0indirect
PyPIruff0.16.6indirect
PyPIshellingham1.5.4indirect
PyPIsix1.17.0indirect
PyPIsse-starlette3.4.3indirect
PyPIstarlette1.3.1indirect
PyPIty0.0.78indirect
PyPItyper0.25.1indirect
PyPItyping-inspection0.4.2indirect
PyPIuv-build0.12.10indirect
PyPIuvicorn0.46.0indirect
PyPIzoo-mcp0.27.0indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 68 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
cryptography48.0.1indirecthigh650.0.0

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 — PyPI.