updated 2026-11-10 04:07 UTC

Orcaslicer MCP

Repository

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 4%
Last push yesterday
Advisories None known
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 58.4/100 (Grade C), ranked #745 of 1374 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; 4% of recent commits are signed; no published advisory affects its latest release (orcaslicer-mcp); last pushed 2026-11-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Orcaslicer 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 Orcaslicer 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/MaxEllis/orcaslicer-mcp, AGPL-3.0, last pushed 2026-11-09. 4% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

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

    • Code Review0
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 0
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases 0
    Token-Permissions 10
    Vulnerabilities 0

  3. Published packages Linked, not attested

    • PyPI orcaslicer-mcp Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: orcaslicer-mcp 0.1.21. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-08-29 OSSF Scorecard: 3.5/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 Orcaslicer 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 Orcaslicer MCP compares in MCP Servers

  1. #404 SeedanceMCP 58.4 ±0
  2. #405 Random Number MCP 58.4 ±0
  3. #406 Orcaslicer MCP 58.4 this agent
  4. #407 webclaw 58.3 −0.1
  5. #408 OrangePro 58.3 −0.1

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

Where the 58.4 comes from

HVTrust dimensions vs the MCP Servers average

58.4 / 100 · 100.0% confidence

Orcaslicer MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.6 / 25
6.2 below avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
11.5 / 17
0.8 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
19.8 / 20
7.6 above avg 12.2
AdoptionLog-scaled stars · package downloads
9.0 / 20
1.4 above avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-10
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-11-10
Mcp Status Changed
Detected MCP server support changed: implemented → none
2026-11-10
Rank Moved
Rank rose 22 spots (#767 → #745)
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
View MCP Servers Report missing data
67.7
Activity sub-score · out of 100
#406
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 →

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

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
97
Forks
23
Last Push
2026-11-09
yesterday
Commits (4 wk)
90
Downloads (7d)
1,480
pypi
HN mentions (30d)
—
Open Issues
1
Rank Change
▲22
was #767

Analysis

Activity Inputs

67.7 / 100
StarsRepository reach
11.9 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
24.4 / 25
CommunityFork signal
6.4 / 20

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 1 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?
4% 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
None detected
No MCP server signal detected.
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
high confidence
Declared
Declared plugin/integration 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-11-10
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-11-10
Mcp Status Changed
Detected MCP server support changed: implemented → none
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
Rank 29Score 3HVTrust 2Grade 2MCP 2Scorecard 1Delisted 1Listed 1Surface 1
2026-11-10
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-11-10
Mcp Status Changed
Detected MCP server support changed: implemented → none
2026-11-10
Rank Moved
Rank rose 22 spots (#767 → #745)
2026-11-10
Activity Score Changed
Activity score up 9pts (59 → 68)
2026-11-08
Rank Moved
Rank dropped 78 spots (#697 → #775)
2026-11-08
Activity Score Changed
Activity score down 8pts (66 → 58)
2026-11-02
Rank Moved
Rank rose 43 spots (#747 → #704)
2026-11-01
Rank Moved
Rank dropped 10 spots (#737 → #747)
2026-10-30
Rank Moved
Rank rose 14 spots (#755 → #741)
2026-10-26
Rank Moved
Rank dropped 10 spots (#746 → #756)
2026-10-21
Rank Moved
Rank dropped 12 spots (#721 → #733)
2026-10-18
Rank Moved
Rank rose 41 spots (#749 → #708)
2026-10-10
Rank Moved
Rank rose 14 spots (#739 → #725)
2026-10-09
Rank Moved
Rank rose 65 spots (#804 → #739)
2026-10-09
Activity Score Changed
Activity score up 8pts (57 → 65)
2026-10-08
Rank Moved
Rank dropped 19 spots (#785 → #804)
2026-10-05
Rank Moved
Rank dropped 11 spots (#764 → #775)
2026-10-01
Rank Moved
Rank dropped 34 spots (#739 → #773)
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)
GitHub → PyPI: orcaslicer-mcp

Embed Badge Badge guide for maintainers →

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