Is build123d MCP safe to use?

build123d MCP has an HVTrust score of 78.5/100 (Grade B), ranked #165 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for build123d MCP?

build123d MCP scores 78.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 94 GitHub stars and is categorized under MCP Servers.

build123d MCP

pzfreo/build123d-mcp

MCP server for build123d to improve AI cognition when creating 3D CAD models

MCP Servers Python Listed Apache-2.0

Is build123d MCP safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 4.1 / 10

Provenance Attested

Signed commits 30%

Last push yesterday

Compare build123d MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: build123d MCP scores 78.5/100 (Grade B), ranked #165 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.1/10; 30% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →

How build123d MCP compares in MCP Servers

#87 Postman MCP Server 78.7 +0.2
#88 Ckan MCP Server 78.7 +0.2
#89 build123d MCP 78.5 this agent
#90 Ai Cli MCP 78.4 −0.1
#91 Semantic Scholar MCP Server 78.2 −0.3

Bars show each HVTrust score; the tick marks build123d MCP’s 78.5.

Where the 78.5 comes from

HVTrust dimensions vs the MCP Servers average

78.5 / 100 · 100.0% confidence

build123d MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

14.1 / 25

3.8 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.0 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

19.2 / 20

7.1 above avg 12.1

AdoptionLog-scaled stars · package downloads

9.2 / 20

2.0 above avg 7.2

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-09-25

Rank Moved

Rank rose 18 spots (#183 → #165)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.1/10. Tighten the weakest checks to improve public safety evidence.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for build123d MCP View MCP Servers Report missing data

64.8

Activity sub-score · out of 100

#89

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-25

yesterday

Commits (4 wk)

Downloads (7d)

2,130

pypi

HN mentions (30d)

—

Open Issues

Rank Change

was #165

Analysis

Activity Inputs

64.8 / 100

StarsRepository reach

11.9 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

22.6 / 25

CommunityFork signal

5.3 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

4.1 / 10

OpenSSF Scorecard · scanned Sep 25, 2026

Signed Commits

30%

of last 100 commits verified

Binary-Artifacts 9

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about build123d MCP

Public supply-chain signals for build123d MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but build123d MCP carries less obvious unverified-evidence risk than projects with thin signals.

Does build123d MCP publish package provenance?

Yes. build123d MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does build123d MCP have an OpenSSF Scorecard?

build123d MCP has an OpenSSF Scorecard score of 4.1/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is build123d MCP actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does build123d MCP use?

build123d MCP ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are build123d MCP's commits signed?

30% of the last 100 commits to build123d MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

build123d MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to build123d MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain build123d MCP?

For maintainers

HVTrust scores build123d MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-25

Rank Moved

Rank rose 18 spots (#183 → #165)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 704 spots (#896 → #192)

2026-09-23

HVTrust Changed

HVTrust up 49.5pts (26.9 → 76.4)

2026-09-22

Newly Listed

First tracked at rank #896

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-11

Rank Moved

Rank dropped 10 spots (#194 → #204)

2026-09-07

Rank Moved

Rank dropped 17 spots (#170 → #187)

2026-09-05

Rank Moved

Rank dropped 39 spots (#132 → #171)

2026-09-03

Grade Changed

Trust grade C → B

2026-09-03

Rank Moved

Rank rose 560 spots (#691 → #131)

2026-09-03

HVTrust Changed

HVTrust up 26.0pts (50.7 → 76.7)

2026-09-02

Grade Changed

Trust grade D → C

2026-09-02

Rank Moved

Rank dropped 10 spots (#681 → #691)

2026-09-01

Scorecard Added

OSSF Scorecard: 4.1/10

2026-09-01

Rank Moved

Rank rose 114 spots (#795 → #681)

2026-09-01

HVTrust Changed

HVTrust up 5.5pts (44.3 → 49.8)

2026-08-31

Rank Moved

Rank dropped 28 spots (#767 → #795)

2026-08-30

Rank Moved

Rank dropped 26 spots (#741 → #767)

2026-08-29

Rank Moved

Rank dropped 47 spots (#694 → #741)

2026-08-28

Rank Moved

Rank dropped 14 spots (#680 → #694)

2026-08-26

Rank Moved

Rank dropped 103 spots (#576 → #679)

2026-08-25

Rank Moved

Rank dropped 12 spots (#564 → #576)

2026-08-24

Rank Moved

Rank dropped 19 spots (#545 → #564)

2026-08-22

Rank Moved

Rank rose 13 spots (#556 → #543)

2026-08-16

Rank Moved

Rank dropped 10 spots (#546 → #556)

2026-08-13

Rank Moved

Rank dropped 11 spots (#533 → #544)

2026-08-12

Rank Moved

Rank rose 11 spots (#544 → #533)

2026-08-10

Rank Moved

Rank dropped 17 spots (#529 → #546)

2026-08-08

Newly Listed

First tracked at rank #528

GitHub → PyPI: build123d-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/build123d-mcp.svg)](https://hvtracker.net/agents/build123d-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/build123d-mcp"><img src="https://hvtracker.net/badge/build123d-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON