CanopiiCanopiiAll serversEnterprise →

roboparts MCP Server Security Report

cc.roboparts/roboparts

688 humanoid robot component entities with 4-dimension compatibility checking. Vendor-neutral.

Security Trust Score
Grade F · Serious issues
Tier 1 · Public sourceHigh confidence · 98%latest v1.1.0 Repository
Declared MCP capabilities
ResourcesPrompts

Run it securely

This server scored F. Run it behind runtime policy enforcement so one bad tool call can't become an incident.

Are you the maintainer?

Verify with GitHub to get alerted whenever lm203688/roboparts changes score — and claim the badge for your README.

Claim this server
1 issue capping this score
  • criticalNo command-injection sinks — 2 occurrences
Reputation0stars0forks0open issuestodaylast commit<1yage

Security controlslatest scored version v1.1.0

Each control is evaluated deterministically with evidence. The score is earned from passing controls; a failed guard caps it.

Model–MCP Runtime Guardrails

  • Warn
    Strict JSON Schema Enforcementschemas not strict

    Tool inputs are constrained (additionalProperties:false), so unexpected arguments can't be smuggled in.

    Fix: Set additionalProperties:false and require explicit parameters on every tool.

  • Pass
    Indirect Prompt Injection (IPI) Defensesguardno injection markers

    Tool/prompt/resource text is free of hidden instructions that could hijack the agent.

  • Pass
    User-in-the-Loop / Approval Scopeguardno destructive tool scope

    No over-broad or destructive tools (arbitrary shell, bulk-delete) that warrant human approval.

  • N/A
    Tool Definition Integrityguardno prior version to diff

    Every consecutive version pair is diffed for new injection markers or destructive scope — a risky diff anywhere in history is a rug-pull (fail, durable); benign description drift warns.

Application Security Checks

  • Fail
    No command-injection sinksguard2 occurrences

    Untrusted tool input reaching a shell yields remote code execution. How many servers fail this?

    scripts/read_metrics.py:28scripts/regression.py:2841

    Fix: Never pass tool arguments to a shell; use argv arrays with shell disabled.

  • Warn
    No path traversalguard33 occurrences

    Naive path checks let tools read/write outside intended directories (EscapeRoute-class).

    functions/_lib/upstream.js:83functions/_lib/upstream.js:87functions/_middleware.js:167functions/_middleware.js:168

    Fix: Resolve to a canonical path and verify containment; reject ../ and symlinks.

  • Warn
    No SSRF sinksguard11 occurrences

    Fetching tool-supplied URLs can pivot into internal networks and metadata services.

    functions/api/payment/creem.js:85mcp-server/index.js:90scripts/deploy.mjs:141scripts/deploy.mjs:156

    Fix: Allow-list destinations; reject arbitrary/loopback/link-local URLs.

  • Warn
    No known-vulnerable dependencies3 of 92 runtime deps vulnerable; worst high

    Runtime dependencies (parsed from the lockfile) are scanned against OSV.dev for published CVEs. Advisory: flagged dependencies lower the score but don't hard-cap it, since transitive reachability is unproven.

    @hono/[email protected] — GHSA-frvp-7c67-39w9[email protected] — GHSA-7p8r-x3mc-p8w7[email protected] — GHSA-8j4g-w8fx-2239

    Fix: Upgrade the flagged dependencies past their fixed versions.

  • Warn
    Declares a licenseno recognized license

    A clear license is required for legal enterprise use.

    Fix: Add a recognized SPDX license (MIT, Apache-2.0, …).

  • Warn
    Has a security policyno security policy

    A SECURITY.md gives a private path to report vulnerabilities.

    Fix: Add SECURITY.md with a disclosure contact and process.

  • Warn
    Adoption & popularitylimited adoption

    A small, capped nudge from stars/downloads — widely-used servers get more eyes on bugs. It can never offset a real security failure.

    Fix: Adoption grows naturally with real-world use; this never gates the score.

  • Pass
    No dynamic code executionguardno sinks found

    eval()/exec()/Function() on tool-derived strings allows arbitrary code execution.

  • Pass
    No unsafe deserializationguardno sinks found

    pickle/yaml.load/etc. on untrusted data can execute code.

  • Pass
    No committed secretsguardno secrets found

    Hardcoded keys/tokens in published source are live credentials an attacker can use.

  • Pass
    Credentials sourced from environmentreads credentials from environment

    Reading secrets from env/secret stores avoids hardcoding them.

  • Pass
    Dependencies pinned (lockfile)lockfile present

    A lockfile makes installs reproducible and resistant to silent dependency swaps.

  • Pass
    Actively maintainedrecent commits

    Unmaintained servers don't receive security fixes.

  • Pass
    Repository not archivedguardactive

    Archived repositories will never be patched.

  • Not checked
    Signed releasesnot evaluated

    Signed releases let consumers verify artifacts weren't tampered with.

  • N/A
    No install/post-install scriptsguardno published package

    install hooks run arbitrary code on every consumer at install time.

  • N/A
    Package name not typosquattingguardno published package

    Names mimicking popular packages are a common malware delivery vector.

  • N/A
    Published with provenanceno published package

    Build provenance attests the artifact was built from the claimed source by CI.

  • N/A
    Established maintainerno published package

    Brand-new / single anonymous maintainers raise takeover and malware risk.

Transport & Trust Model

  • Warn
    IAM / Authentication Scopingno authentication handling detected

    OAuth 2.1 / Protected Resource Metadata gates who can invoke tools.

    Fix: Implement OAuth 2.1 with a .well-known/oauth-protected-resource document.

  • Warn
    Execution Sandboxingruns natively (no container image)

    A container/sandbox image limits blast radius; a server that runs natively has full host access.

    Fix: Ship a Dockerfile/Containerfile (or document a sandboxed run) so the server runs isolated.

  • Pass
    Transport Encryption (TLS)guardall remotes use HTTPS

    Plaintext HTTP exposes traffic and bearer tokens to interception.

  • Pass
    Network Exposureno bind-all detected

    Binding 0.0.0.0 or exposing debug inspectors widens the attack surface.

  • N/A
    Live Endpoint Reachablenot dynamically scanned

    A dynamic scan connected to the declared remote endpoint and it responded — verified live, not a dead URL.

  • N/A
    Authentication Enforced (live)not dynamically scanned

    If the server declares auth is required, it must actually reject anonymous clients. Serving tools to unauthenticated callers is a real exposure.

Embed this score

Add the live badge to your README — it updates automatically on every rescan.

Canopii Trust Score badge preview
markdown[![Canopii Trust Score](https://index.canopii.dev/api/badge/cc.roboparts/roboparts)](https://index.canopii.dev/server/cc.roboparts/roboparts)
html<a href="https://index.canopii.dev/server/cc.roboparts/roboparts"><img src="https://index.canopii.dev/api/badge/cc.roboparts/roboparts" alt="Canopii Trust Score" /></a>

Versions

VersionScoreStatus
v1.1.0latest15Fscored

Wondering how this compares? The MCP Security Index tracks grade distribution, committed secrets, and missing authentication across the whole ecosystem, refreshed monthly.