CanopiiCanopiiAll serversEnterprise →

designesy-org MCP Server Security Report

io.github.LE-VAI/designesy-org

Score any URL against a real design contract — 40 checks, A-F grade, token + motion validation.

Security Trust Score
Grade F · Serious issues
Tier 1 · Public sourceHigh confidence · 93%latest v1.10.0 Repository
Declared MCP capabilities
Prompts

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 LE-VAI/designesy-org changes score — and claim the badge for your README.

Claim this server
2 issues capping this score
  • criticalNo command-injection sinks — 43 occurrences
  • highTool descriptions free of injection markers — 1 marker(s) across 1 tool(s)

The short answer

Is designesy-org safe to use?
designesy-org scores 14/100 (grade F) on the Canopii Trust Index, and carries 2 confirmed security failures that cap its score: No command-injection sinks and Tool descriptions free of injection markers. It passes 12 of the 27 controls that apply to it.
What security issues does designesy-org have?
designesy-org fails 2 controls: No command-injection sinks and Tool descriptions free of injection markers. Each failure on this page carries the evidence behind it — the file and line, dependency, or CVE that decided it.
How reliable is the security score for designesy-org?
We could evaluate 93% of the controls that apply to designesy-org. Scores are deterministic — the same source always produces the same score — and a partially-scannable server cannot present a high one, because confidence caps the result. The scanner is open source, so this score can be reproduced independently.
Does designesy-org have any security advisories?
designesy-org has 1 non-scoring advisory — observations worth a human review that deliberately do not affect the deterministic score, since they can be noisy.
How was designesy-org scored?
Its published source was scanned against a fixed catalog of weighted security controls covering code safety, committed secrets, dependency vulnerabilities, tool-description integrity, authentication and transport, and maintenance. A confirmed flaw caps the score outright regardless of what else passes. The full rubric is published.
Reputation0stars0forks2open issues1d agolast commit<1yage

Security controlslatest scored version v1.10.0

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

Model–MCP Runtime Guardrails

  • Fail
    Indirect Prompt Injection (IPI) Defensesguard1 marker(s) across 1 tool(s)

    Tool/prompt/resource text is free of hidden instructions that could hijack the agent. How many servers fail this?

    designesy_monitor_score — exfiltration directive

    Fix: Remove hidden directives, HTML/comment instructions, and override phrasing from descriptions.

  • 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.

  • Warn
    Tool Definition Integrityguard1 tool description(s) drifted after publish (no risk signals in 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.

    ${c.name} contract

    Fix: Never add hidden directives or destructive scope to an already-published tool; document description changes in release notes.

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

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

Application Security Checks

  • Fail
    No command-injection sinksguard43 occurrences

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

    apps/site/app/api/compare/route.ts:59apps/site/app/api/compare/route.ts:63apps/site/app/api/compare/route.ts:125apps/site/app/api/compare/route.ts:129

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

  • Warn
    No path traversalguard72 occurrences

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

    apps/site/app/api/compare/route.ts:96apps/site/app/api/compare/route.ts:109apps/site/app/api/drift/route.ts:151apps/site/app/api/drift/route.ts:164

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

  • Warn
    No SSRF sinksguard22 occurrences

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

    apps/site/app/api/compare/route.ts:524apps/site/app/api/compare/route.ts:529apps/site/app/api/cron/rescore/route.ts:34apps/site/app/api/leaderboard/submit/route.ts:78

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

  • Warn
    Established maintainerrecently published

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

    Fix: Publish under an established account/org; add multiple maintainers.

  • 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
    No known-vulnerable dependencies186 runtime deps, no known CVEs

    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.

  • Pass
    Dependencies pinned (lockfile)lockfile present

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

  • Pass
    Package name not typosquattingguarddistinct package name

    Names mimicking popular packages are a common malware delivery vector.

  • Pass
    Actively maintainedrecent commits

    Unmaintained servers don't receive security fixes.

  • Pass
    Repository not archivedguardactive

    Archived repositories will never be patched.

  • Pass
    Declares a licenseMIT

    A clear license is required for legal enterprise use.

  • Not checked
    No install/post-install scriptsguardnot determinable from PyPI metadata

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

  • Not checked
    Published with provenancenot determinable

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

  • Not checked
    Signed releasesnot evaluated

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

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.

  • Warn
    Network Exposurebinds 0.0.0.0

    Binding 0.0.0.0 or exposing debug inspectors widens the attack surface.

    Fix: Bind to 127.0.0.1 by default; never ship open debug endpoints.

  • Pass
    Transport Encryption (TLS)guardall remotes use HTTPS

    Plaintext HTTP exposes traffic and bearer tokens to interception.

  • 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.

AI-flagged — for review

Observations from an AI review of tool descriptions. These are advisory only and do not affect the score — they can be noisy and need human judgement.

  • info
    Tool "${c.name} contract" description changed after publish

    Benign definition drift: the description changed vs the prior version with no risk signals in the diff. Clients approve tools by name and don't re-review on update, so the change is invisible to existing grants.

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/io.github.LE-VAI/designesy-org)](https://index.canopii.dev/server/io.github.LE-VAI/designesy-org)
html<a href="https://index.canopii.dev/server/io.github.LE-VAI/designesy-org"><img src="https://index.canopii.dev/api/badge/io.github.LE-VAI/designesy-org" alt="Canopii Trust Score" /></a>

Versions

VersionScoreStatus
v1.10.0latest14Fscored
v1.9.439Fscored
v1.9.339Fscored
v1.9.136Fscored
v1.8.336Fscored
v1.7.039Fscored
v1.5.039Fscored
v1.4.239Fscored
v1.3.138Fscored

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