MCP server · trust report

io.github.Krv-Labs/topos

2 checks that ran failed — permission scope and version behavior — so this release can’t be trusted as-is.

Publisher
io.github.Krv-Labs
Repository
github.com/Krv-Labs/topos
Install
pypi:topos-mcp, pypi:topos-mcp, pypi:topos-mcp, pypi:topos-mcp, pypi:topos-mcp, pypi:topos-mcp, pypi:topos-mcp, pypi:topos-mcp, pypi:topos-mcp, pypi:topos-mcp, pypi:topos-mcp, pypi:topos-mcp, pypi:topos-mcp, pypi:topos-mcp
Versions
14
Inspected
5 of 6 checks · 75%
Scored
2026-09-02 · 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 checks2 clean3 flagged1 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

    pass25% of grade

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

    Python build script has no build-time network/exec; repository linkage verified

  • Credential hygiene

    pass15% of grade

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

    Reads secrets from the environment (e.g. extensions/vscode/scripts/check-vsix-size.js) — the recommended intake shape. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.

  • Permission scope

    fail15% of grade

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

    HIGH: downloads and pipes straight to a shell (topos/cli/update.py: pipes a download into a shell). has both shell/exec and destructive filesystem writes (extensions/vscode/scripts/stage-binary.js: imports child_process and calls exec/spawn; extensions/vscode/scripts/stage-binary.js: destructive/writing fs.* call (write/unlink/rm/chmod/rename)). discloses shell/exec capability: 7 files (extensions/vscode/scripts/stage-binary.js, extensions/vscode/src/extension.ts, topos/cli/update.py, +4 more) discloses broad/destructive filesystem access: 5 files (extensions/vscode/scripts/stage-binary.js, extensions/vscode/scripts/test-stage-binary.js, extensions/vscode/src/runtime.ts, +2 more) 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 0.4.4 (minor bump): new capability primitive(s) in source: child_process, dynamic-eval, fs-write, subprocess; new hardcoded outbound host/BCC destination(s): 127.0.0.1, benchmarksgame-team.pages.debian.net, code.visualstudio.com, docs.krv.ai, docs.python.org, github.com, krv.ai, pypi.org, raw.githubusercontent.com, salsa.debian.org, x.

  • Transport config

    warn10% of grade

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

    manifest/source references tracking behavior — disclosure

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
v0.5.1 · current2026-08-09 C705/6 · 75%B→C in v0.5.1
v0.4.42026-08-05 B1003/6 · 55%±0
v0.4.32026-07-28 B804/6 · 65%C→B in v0.4.3
v0.4.22026-07-26 C705/6 · 75%B→C in v0.4.2
v0.4.12026-07-25 B1004/6 · 65%±0
v0.3.122026-07-21 B805/6 · 75%±0
v0.3.112026-07-15 B804/6 · 65%