updated 2026-11-10 04:07 UTC

build123d MCP

Repository

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

MCP Servers Python Listed Apache-2.0

Is build123d MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.1 / 10
Provenance Attested
Signed commits 31%
Last push yesterday
Advisories None known
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 72.9/100 (Grade B), ranked #310 of 1374 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; 31% of recent commits are signed; no published advisory affects its latest release (build123d-mcp); last pushed 2026-11-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How build123d MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships build123d MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/pzfreo/build123d-mcp, Apache-2.0, last pushed 2026-11-09. 31% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.1/10 (scanned Nov 9, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    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

  3. Published packages Linked and attested

    • PyPI build123d-mcp Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: build123d-mcp 0.3.91. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-09-01 OSSF Scorecard: 4.1/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues build123d MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How build123d MCP compares in MCP Servers

  1. #181 Yantrikdb MCP 73.0 +0.1
  2. #182 Screaming Frog SEO Spider MCP Server 73.0 +0.1
  3. #183 build123d MCP 72.9 this agent
  4. #184 Arm MCP Server 72.8 −0.1
  5. #185 MCP Memory Service 72.8 −0.1

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

Where the 72.9 comes from

HVTrust dimensions vs the MCP Servers average

72.9 / 100 · 100.0% confidence

build123d MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
14.2 / 25
3.4 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
12.0 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
13.3 / 20
1.1 above avg 12.2
AdoptionLog-scaled stars · package downloads
9.4 / 20
1.8 above avg 7.6

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-11-09
Rank Moved
Rank rose 25 spots (#332 → #307)
2026-11-09
Activity Score Changed
Activity score up 6pts (47 → 53)
2026-10-25
Rank Moved
Rank dropped 62 spots (#239 → #301)
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
View MCP Servers Report missing data
52.8
Activity sub-score · out of 100
#183
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 →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
146
Forks
20
Last Push
2026-11-09
yesterday
Commits (4 wk)
4?
Downloads (7d)
1,406
pypi
HN mentions (30d)
—
Open Issues
59
Rank Change
▼3
was #307

Analysis

Activity Inputs

52.8 / 100
StarsRepository reach
13.0 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
8.7 / 25
CommunityFork signal
6.1 / 20

Common questions about build123d MCP

build123d MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
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?
31% 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
Rank 22HVTrust 4Grade 3Score 2Scorecard 1Delisted 1Listed 1Provenance 1MCP 1
2026-11-09
Rank Moved
Rank rose 25 spots (#332 → #307)
2026-11-09
Activity Score Changed
Activity score up 6pts (47 → 53)
2026-10-25
Rank Moved
Rank dropped 62 spots (#239 → #301)
2026-10-25
HVTrust Changed
HVTrust down 3.4pts (76.0 → 72.6)
2026-10-25
Activity Score Changed
Activity score down 10pts (59 → 48)
2026-10-24
Rank Moved
Rank dropped 29 spots (#210 → #239)
2026-10-15
Rank Moved
Rank rose 17 spots (#219 → #202)
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)
GitHub → PyPI: build123d-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 72.9 Grade B
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.4 · Raw JSON