Is build123d MCP safe to use?

build123d MCP has an HVTrust score of 44.2/100 (Grade D), ranked #546 of 1283 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 44.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 42 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 Grade D Listed Apache-2.0

44.2/100

Rank #546 of 1283

Compare build123d MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-08-11 · 1d ago

Recent change

Rank +1

Is build123d MCP safe? build123d MCP scores 44.2/100 (Grade D), ranked #546 of 1283 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; no OSSF Scorecard result yet; 38% of recent commits are signed; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#198 Npm Sentinel MCP — 44.3 (D) → #199 MCP Youtube — 44.2 (D) → #201 MCP Document Converter — 44.1 (D) → #202 Dynatrace MCP — 43.9 (D) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-08-10

Rank Moved

Rank dropped 17 spots (#529 → #546)

2026-08-08

Newly Listed

First tracked at rank #528

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

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

56.9

Activity sub-score · out of 100

#200

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 D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars

Forks

Last Push

2026-08-11

yesterday

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #544

Analysis

HVTrust Dimensions vs MCP Servers

44.2 / 100 · 67.0% confidence

build123d MCP MCP Servers average (761 agents)

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

9.4 / 25

4.4 above avg 5.0

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.7 above avg 13.3

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

in line with avg 8.8

Maintenance60% last-push freshness · 40% commit activity

17.5 / 20

5.1 above avg 12.4

AdoptionLog-scaled stars · package downloads

3.9 / 20

1.9 below avg 5.8

Activity Inputs

56.9 / 100

StarsRepository reach

9.8 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

17.4 / 25

CommunityFork signal

4.7 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

—

Not available

Signed Commits

38%

of last 100 commits verified

Is build123d MCP safe?

Public trust evidence for build123d MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

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?

No OpenSSF Scorecard data is currently published for build123d MCP. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.

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?

38% 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

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-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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON