io.github.mariorojasmz/apolo-cad
PYPI · APOLO-CAD
Agent-native parametric 3D CAD: model machines, validate them and emit shop drawings
Available components
Last scanned (5 hours ago)
Scores higher than 30% of PyPI servers
Category Design and Media
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 20 of 104 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 69 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 +3
- CVE-2026-59205 no longer affects this package ▲ security
- CVE-2026-55798 no longer affects this package ▲ security
- CVE-2026-59199 no longer affects this package ▲ security
- CVE-2026-54058 no longer affects this package ▲ security
- CVE-2026-54060 no longer affects this package ▲ security
- CVE-2026-59200 no longer affects this package ▲ security
- CVE-2026-59204 no longer affects this package ▲ security
- CVE-2026-55379 no longer affects this package ▲ security
- CVE-2026-59197 no longer affects this package ▲ security
- CVE-2026-59203 no longer affects this package ▲ security
- CVE-2026-59198 no longer affects this package ▲ security
- CVE-2026-54059 no longer affects this package ▲ security
- CVE-2026-55380 no longer affects this package ▲ security
- Known CVEs: fail → pass ▲ security
- 13 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 12 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +3
- License: fail → pass ▲ functional
- Licence: MIT functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 20 Sept 26 −3
- CVE-2026-59200 affects this package: high ▼ security
- CVE-2026-54059 affects this package: high ▼ security
- CVE-2026-59197 affects this package: high ▼ security
- CVE-2026-59199 affects this package: high ▼ security
- CVE-2026-55379 affects this package: high ▼ security
- CVE-2026-54060 affects this package: high ▼ security
- CVE-2026-59204 affects this package: high ▼ security
- CVE-2026-59198 affects this package: high ▼ security
- CVE-2026-59205 affects this package: high ▼ security
- CVE-2026-55798 affects this package: high ▼ security
- CVE-2026-54058 affects this package: high ▼ security
- CVE-2026-55380 affects this package: high ▼ security
- CVE-2026-59203 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Analysed pypi/apolo-cad@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 104 packages
| Packages resolved | 104 |
|---|---|
| Stale | 14 |
| No linked repository | 6 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
How do I install the io.github.mariorojasmz/apolo-cad MCP server?
io.github.mariorojasmz/apolo-cad runs locally as a PyPI package, launched with uvx apolo-cad. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · apolo-cad
claude mcp add mariorojasmz-apolo-cad -- uvx apolo-cad
What is the io.github.mariorojasmz/apolo-cad MCP server?
io.github.mariorojasmz/apolo-cad is an MCP server listed in the public MCP registry as io.github.mariorojasmz/apolo-cad. Agent-native parametric 3D CAD: model machines, validate them and emit shop drawings. This page covers its PyPI package (apolo-cad).
Is the io.github.mariorojasmz/apolo-cad MCP server safe to use?
io.github.mariorojasmz/apolo-cad scores 39 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
Is the io.github.mariorojasmz/apolo-cad MCP server still maintained?
io.github.mariorojasmz/apolo-cad is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.mariorojasmz/apolo-cad MCP server under?
io.github.mariorojasmz/apolo-cad declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.