licensing MCP Server Security Report
MCP-native software license keys for AI-built apps — EARLY ACCESS (waitlist, not built yet).
Host com.kywio/licensing in a governed environment — SSO in front, every tool call attributed and audited.
Security controlslatest scored version v0.0.1
Each control is evaluated deterministically with evidence. The score is earned from passing controls; a failed guard caps it.
Security controlslatest scored version v0.0.1
Each control is evaluated deterministically with evidence. The score is earned from passing controls; a failed guard caps it.
Model–MCP Runtime Guardrails
- WarnStrict 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.
- PassIndirect Prompt Injection (IPI) Defensesguardno injection markers
Tool/prompt/resource text is free of hidden instructions that could hijack the agent.
- PassUser-in-the-Loop / Approval Scopeguardno destructive tool scope
No over-broad or destructive tools (arbitrary shell, bulk-delete) that warrant human approval.
- N/ATool Definition Stabilityguardno prior version to diff
Tool definitions did not change after publish — no post-approval rug-pull.
Application Security Checks
- WarnNo SSRF sinksguard1 occurrence
Fetching tool-supplied URLs can pivot into internal networks and metadata services.
bench/aeo/measure.py:34Fix: Allow-list destinations; reject arbitrary/loopback/link-local URLs.
- WarnDeclares a licenseno recognized license
A clear license is required for legal enterprise use.
Fix: Add a recognized SPDX license (MIT, Apache-2.0, …).
- WarnHas 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.
- WarnAdoption & 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.
- PassNo command-injection sinksguardno sinks found
Untrusted tool input reaching a shell yields remote code execution.
- PassNo dynamic code executionguardno sinks found
eval()/exec()/Function() on tool-derived strings allows arbitrary code execution.
- PassNo path traversalguardno sinks found
Naive path checks let tools read/write outside intended directories (EscapeRoute-class).
- PassNo unsafe deserializationguardno sinks found
pickle/yaml.load/etc. on untrusted data can execute code.
- PassNo committed secretsguardno secrets found
Hardcoded keys/tokens in published source are live credentials an attacker can use.
- PassCredentials sourced from environmentreads credentials from environment
Reading secrets from env/secret stores avoids hardcoding them.
- PassDependencies pinned (lockfile)lockfile present
A lockfile makes installs reproducible and resistant to silent dependency swaps.
- PassActively maintainedrecent commits
Unmaintained servers don't receive security fixes.
- PassRepository not archivedguardactive
Archived repositories will never be patched.
- Not checkedNo known-vulnerable dependenciesno lockfile found
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.
- Not checkedSigned releasesnot evaluated
Signed releases let consumers verify artifacts weren't tampered with.
- N/ANo install/post-install scriptsguardno published package
install hooks run arbitrary code on every consumer at install time.
- N/APackage name not typosquattingguardno published package
Names mimicking popular packages are a common malware delivery vector.
- N/APublished with provenanceno published package
Build provenance attests the artifact was built from the claimed source by CI.
- N/AEstablished maintainerno published package
Brand-new / single anonymous maintainers raise takeover and malware risk.
Transport & Trust Model
- WarnIAM / 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.
- WarnNetwork 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.
- PassTransport Encryption (TLS)guardall remotes use HTTPS
Plaintext HTTP exposes traffic and bearer tokens to interception.
- PassExecution Sandboxingcontainerized
A container/sandbox image limits blast radius; a server that runs natively has full host access.
- N/ALive Endpoint Reachablenot dynamically scanned
A dynamic scan connected to the declared remote endpoint and it responded — verified live, not a dead URL.
- N/AAuthentication 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.
[](https://index.canopii.dev/server/com.kywio/licensing)<a href="https://index.canopii.dev/server/com.kywio/licensing"><img src="https://index.canopii.dev/api/badge/com.kywio/licensing" alt="Canopii Trust Score" /></a>Versions
| Version | Score | Status | Published |
|---|---|---|---|
| v0.0.1latest | 88B | scored | 7/13/2026 |