MCP server · trust report

io.github.kyrylopr/lenspr

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

Publisher
io.github.kyrylopr
Repository
github.com/kyrylopr/lenspr
Install
pypi:lenspr
Versions
1
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

    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

    warn15% of grade

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

    tests/test_helpers.py: assigns a literal to api_key (sk-a…56 (len 12)) — non-provider secret literal; prefer environment intake. tests/test_helpers.py: assigns a literal to apikey (sk-a…56 (len 12)) — non-provider secret literal; prefer environment intake. tests/test_helpers.py: assigns a literal to token (eyJh…ad (len 28)) — non-provider secret literal; prefer environment intake. Reads secrets from the environment (e.g. lenspr/pytest_tracer.py) — the recommended intake shape.

  • Permission scope

    warn15% of grade

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

    has both shell/exec and network egress — capable of download-and-run, though no such path was observed (lenspr/doctor.py: subprocess.* call; lenspr/parsers/typescript_parser.py: outbound HTTP/socket call). has both shell/exec and destructive filesystem writes (lenspr/doctor.py: subprocess.* call; lenspr/context.py: open(…, 'w'/'a'/'x') write-mode file access). discloses shell/exec capability: 10 files (lenspr/doctor.py, lenspr/monorepo.py, lenspr/parsers/node_resolver.py, +7 more) discloses broad/destructive filesystem access: lenspr/context.py: open(…, 'w'/'a'/'x') write-mode file access discloses broad/destructive filesystem access: lenspr/doctor.py: recursive glob ('**') from a broad root Capability DISCLOSURE, not a verdict: static analysis sees the primitive is present and reachable, not whether its use is attacker-controlled.

  • Version behavior

    unscannable10% of grade

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

    no prior version to diff (first sight of io.github.kyrylopr/[email protected]); version-drift / rug-pull cannot be evaluated. Cold-start risk is covered by point-in-time checks (injection_surface, supply_chain, credential_hygiene), not here.

  • Transport config

    fail10% of grade

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

    source performs runtime self-update / download-and-execute (bypasses version_behavior); 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.1.1 · current2026-02-23 B754/6 · 65%