MCP server · trust report

io.github.MikkoParkkola/trvl

1 check that ran failed — version behavior — so this release can’t be trusted as-is.

Publisher
io.github.MikkoParkkola
Repository
github.com/MikkoParkkola/trvl
Install
oci:ghcr.io/mikkoparkkola/trvl:1.10.0, oci:ghcr.io/mikkoparkkola/trvl:1.11.0, oci:ghcr.io/mikkoparkkola/trvl:1.11.1, oci:ghcr.io/mikkoparkkola/trvl:1.12.0, oci:ghcr.io/mikkoparkkola/trvl:1.12.1, oci:ghcr.io/mikkoparkkola/trvl:1.12.2, oci:ghcr.io/mikkoparkkola/trvl:1.13.0, oci:ghcr.io/mikkoparkkola/trvl:1.13.1, oci:ghcr.io/mikkoparkkola/trvl:1.15.0, npm:trvl-mcp, oci:ghcr.io/mikkoparkkola/trvl:1.16.0, npm:trvl-mcp, oci:ghcr.io/mikkoparkkola/trvl:1.17.0, npm:trvl-mcp, oci:ghcr.io/mikkoparkkola/trvl:1.17.1, npm:trvl-mcp, oci:ghcr.io/mikkoparkkola/trvl:1.17.2, npm:trvl-mcp, oci:ghcr.io/mikkoparkkola/trvl:1.17.3, npm:trvl-mcp, oci:ghcr.io/mikkoparkkola/trvl:1.17.4, npm:trvl-mcp, oci:ghcr.io/mikkoparkkola/trvl:1.17.5, npm:trvl-mcp, oci:ghcr.io/mikkoparkkola/trvl:1.17.7, npm:trvl-mcp, oci:ghcr.io/mikkoparkkola/trvl:1.18.0, npm:trvl-mcp, oci:ghcr.io/mikkoparkkola/trvl:1.19.0, npm:trvl-mcp, oci:ghcr.io/mikkoparkkola/trvl:1.19.1, npm:trvl-mcp, oci:ghcr.io/mikkoparkkola/trvl:1.2.3, oci:ghcr.io/mikkoparkkola/trvl:1.20.0, npm:trvl-mcp, oci:ghcr.io/mikkoparkkola/trvl:1.3.0, oci:ghcr.io/mikkoparkkola/trvl:1.4.1, oci:ghcr.io/mikkoparkkola/trvl:1.5.0, oci:ghcr.io/mikkoparkkola/trvl:1.6.0, oci:ghcr.io/mikkoparkkola/trvl:1.7.0, oci:ghcr.io/mikkoparkkola/trvl:1.8.0, oci:ghcr.io/mikkoparkkola/trvl:1.8.2, oci:ghcr.io/mikkoparkkola/trvl:1.9.0, oci:ghcr.io/mikkoparkkola/trvl:1.9.1, oci:ghcr.io/mikkoparkkola/trvl:1.9.2, oci:ghcr.io/mikkoparkkola/trvl:1.21.0, npm:trvl-mcp, oci:ghcr.io/mikkoparkkola/trvl:1.21.1, npm:trvl-mcp, oci:ghcr.io/mikkoparkkola/trvl:1.21.2, npm:trvl-mcp, oci:ghcr.io/mikkoparkkola/trvl:1.21.3, npm:trvl-mcp, oci:ghcr.io/mikkoparkkola/trvl:1.21.4, npm:trvl-mcp
Versions
37
Inspected
4 of 6 checks · 65%
Scored
2026-09-03 · rubric 1.0.0

What we checked

Six static checks, weighted by risk. Every result reflects only what could be observed in the published package and repository — never intent.

6 checks1 clean3 flagged2 not inspected
  • Injection surface

    unscannable25% of grade

    Tool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).

    No tool descriptions, server instructions, prompts, or resources were fetched; nothing to scan for injection.

  • Supply chain

    warn25% of grade

    Package provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.

    install hook "postinstall" present and not a recognized benign build command

  • Credential hygiene

    pass15% of grade

    How the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.

    No hardcoded secrets, secret-shaped tool parameters, or leaked keys found. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.

  • Permission scope

    warn15% of grade

    Declared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.

    has both shell/exec and destructive filesystem writes (bin/install.js: imports child_process and calls exec/spawn; bin/install.js: destructive/writing fs.* call (write/unlink/rm/chmod/rename)). discloses shell/exec capability: bin/install.js: imports child_process and calls exec/spawn discloses shell/exec capability: bin/trvl-mcp.js: imports child_process and calls exec/spawn discloses broad/destructive filesystem access: bin/install.js: destructive/writing fs.* call (write/unlink/rm/chmod/rename) Capability DISCLOSURE, not a verdict: static analysis sees the primitive is present and reachable, not whether its use is attacker-controlled.

  • Version behavior

    fail10% of grade

    Diff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).

    vs prior 1.21.2 (patch bump): new capability primitive(s) in source: child_process, fs-write; new hardcoded outbound host/BCC destination(s): github.com.

  • Transport config

    unscannable10% of grade

    Remote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.

    local stdio server: no remote transport or auth surface, and no phone-home/telemetry signal found in source. Absence of transport findings is NOT a safety guarantee — phone-home hosts can be constructed at runtime and defeat static analysis.

Version history

Each release plotted by grade against the safe line at B. A version that sinks below the line has lost its trusted standing — the shape of a rug-pull.

VersionPublishedGradeScoreInspectedChange
v1.21.4 · current2026-08-12 C704/6 · 65%B→C in v1.21.4
v1.21.22026-08-10 B87.53/6 · 55%±0
v1.21.12026-08-10 B804/6 · 65%±0
v1.21.02026-08-08 B804/6 · 65%C→B in v1.21.0
v1.20.02026-07-13 C72.54/6 · 80%B→C in v1.20.0
v1.19.12026-07-10 B803/6 · 55%±0
v1.17.42026-06-27 B803/6 · 55%insf→B in v1.17.4
v1.9.22026-06-14 insufficient1/6 · 25%