io.github.trackly-app/trackly v0.14.1
This server scored F. Run it behind runtime policy enforcement so one bad tool call can't become an incident.
- criticalNo command-injection sinks — 2 occurrences
- highTool descriptions free of injection markers — 1 marker(s) across 1 tool(s)
Security controls
Deterministic, evidence-backed. Score earned from passing controls; a failed guard caps it.
Security controls
Deterministic, evidence-backed. Score earned from passing controls; a failed guard caps it.
Model–MCP Runtime Guardrails
- FailIndirect 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?
trackly_checkpoint_apply_batch — exfiltration directiveFix: Remove hidden directives, HTML/comment instructions, and override phrasing from descriptions.
- 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.
- PassTool Definition Integrityguardtool definitions stable; no risky changes in version history
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.
- PassUser-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
- FailNo command-injection sinksguard2 occurrences
Untrusted tool input reaching a shell yields remote code execution. How many servers fail this?
lib/agent.js:233mcp/analytics.js:542Fix: Never pass tool arguments to a shell; use argv arrays with shell disabled.
- WarnNo path traversalguard4 occurrences
Naive path checks let tools read/write outside intended directories (EscapeRoute-class).
lib/agent.js:621lib/agent.js:631mcp/analytics.js:186mcp/analytics.js:550Fix: Resolve to a canonical path and verify containment; reject ../ and symlinks.
- WarnNo SSRF sinksguard2 occurrences
Fetching tool-supplied URLs can pivot into internal networks and metadata services.
lib/client.js:756lib/client.js:878Fix: Allow-list destinations; reject arbitrary/loopback/link-local URLs.
- WarnEstablished maintainersingle maintainer
Brand-new / single anonymous maintainers raise takeover and malware risk.
Fix: Publish under an established account/org; add multiple maintainers.
- 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.
- PassNo dynamic code executionguardno sinks found
eval()/exec()/Function() on tool-derived strings allows arbitrary code execution.
- 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.
- PassNo known-vulnerable dependencies97 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.
- PassDependencies pinned (lockfile)lockfile present
A lockfile makes installs reproducible and resistant to silent dependency swaps.
- PassNo install/post-install scriptsguardno install scripts
install hooks run arbitrary code on every consumer at install time.
- PassPackage name not typosquattingguarddistinct package name
Names mimicking popular packages are a common malware delivery vector.
- PassPublished with provenancepublished with provenance
Build provenance attests the artifact was built from the claimed source by CI.
- PassActively maintainedrecent commits
Unmaintained servers don't receive security fixes.
- PassRepository not archivedguardactive
Archived repositories will never be patched.
- PassDeclares a licenseMIT
A clear license is required for legal enterprise use.
- PassAdoption & popularityestablished adoption
A small, capped nudge from stars/downloads — widely-used servers get more eyes on bugs. It can never offset a real security failure.
- Not checkedSigned releasesnot evaluated
Signed releases let consumers verify artifacts weren't tampered with.
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.
- WarnExecution 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.
- PassTransport Encryption (TLS)guardall remotes use HTTPS
Plaintext HTTP exposes traffic and bearer tokens to interception.
- PassNetwork Exposureno bind-all detected
Binding 0.0.0.0 or exposing debug inspectors widens the attack surface.
- 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.