Is Orcaslicer MCP safe to use?

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

What is the trust score for Orcaslicer MCP?

Orcaslicer MCP scores 56.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 55 GitHub stars and is categorized under MCP Servers.

Orcaslicer MCP

MaxEllis/orcaslicer-mcp

OrcaSlicer MCP — drive OrcaSlicer from Claude or any MCP client: load models, tune settings, slice, analyze

MCP Servers Python Listed AGPL-3.0

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

OSSF Scorecard 3.5 / 10

Provenance None

Signed commits 0%

Last push 4d ago

Compare Orcaslicer MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Orcaslicer MCP scores 56.9/100 (Grade C), ranked #719 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.5/10; recent commits are unsigned; last pushed 2026-09-22. Every point is earned from checkable signals — never paid placement. How scoring works →

How Orcaslicer MCP compares in MCP Servers

Bars show each HVTrust score; the tick marks Orcaslicer MCP’s 56.9.

Where the 56.9 comes from

HVTrust dimensions vs the MCP Servers average

56.9 / 100 · 100.0% confidence

Orcaslicer MCP MCP Servers average (775 agents)

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

4.4 / 25

5.9 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.5 / 17

0.7 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

17.9 / 20

5.8 above avg 12.1

AdoptionLog-scaled stars · package downloads

7.3 / 20

in line with avg 7.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank rose 203 spots (#904 → #701)

Maintainer Checklist

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

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

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 Orcaslicer MCP View MCP Servers Report missing data

59.5

Activity sub-score · out of 100

#398

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 C 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-22

4 days ago

Commits (4 wk)

Downloads (7d)

212

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼3

was #716

Analysis

Activity Inputs

59.5 / 100

StarsRepository reach

10.5 / 30

FreshnessLast push recency

24.4 / 25

ActivityRecent commits

19.4 / 25

CommunityFork signal

5.0 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.5 / 10

OpenSSF Scorecard · scanned Sep 20, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 10

Vulnerabilities 9

Common questions about Orcaslicer MCP

Orcaslicer 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 Orcaslicer MCP publish package provenance?

No published build provenance is currently detected for Orcaslicer MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Orcaslicer MCP have an OpenSSF Scorecard?

Orcaslicer MCP has an OpenSSF Scorecard score of 3.5/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 Orcaslicer MCP actively maintained?

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

What license does Orcaslicer MCP use?

Orcaslicer MCP ships under AGPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Orcaslicer MCP's commits signed?

0% of the last 100 commits to Orcaslicer 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

medium confidence

Implemented

Orcaslicer MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

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 Orcaslicer 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

Maintain Orcaslicer MCP?

For maintainers

HVTrust scores Orcaslicer 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-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank rose 203 spots (#904 → #701)

2026-09-23

HVTrust Changed

HVTrust up 30.7pts (26.8 → 57.5)

2026-09-22

Newly Listed

First tracked at rank #904

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-14

Rank Moved

Rank dropped 11 spots (#682 → #693)

2026-09-08

Rank Moved

Rank rose 53 spots (#737 → #684)

2026-09-07

Rank Moved

Rank dropped 50 spots (#687 → #737)

2026-09-06

Rank Moved

Rank dropped 36 spots (#651 → #687)

2026-09-05

Rank Moved

Rank dropped 76 spots (#575 → #651)

2026-09-04

Rank Moved

Rank dropped 21 spots (#554 → #575)

2026-09-02

Rank Moved

Rank dropped 24 spots (#536 → #560)

2026-09-01

Rank Moved

Rank dropped 13 spots (#523 → #536)

2026-08-31

Rank Moved

Rank dropped 31 spots (#492 → #523)

2026-08-29

Scorecard Added

OSSF Scorecard: 3.5/10

2026-08-29

Grade Changed

Trust grade D → C

2026-08-29

Rank Moved

Rank rose 394 spots (#893 → #499)

2026-08-29

HVTrust Changed

HVTrust up 21.5pts (34.1 → 55.6)

2026-08-28

Rank Moved

Rank dropped 31 spots (#862 → #893)

2026-08-27

Rank Moved

Rank dropped 28 spots (#834 → #862)

2026-08-26

Rank Moved

Rank dropped 108 spots (#726 → #834)

2026-08-19

Rank Moved

Rank dropped 10 spots (#707 → #717)

2026-08-16

Rank Moved

Rank dropped 13 spots (#685 → #698)

2026-08-10

Rank Moved

Rank dropped 30 spots (#661 → #691)

2026-08-08

Newly Listed

First tracked at rank #659

GitHub → PyPI: orcaslicer-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/orcaslicer-mcp.svg)](https://hvtracker.net/agents/orcaslicer-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/orcaslicer-mcp"><img src="https://hvtracker.net/badge/orcaslicer-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