MCP server · trust report

io.github.D4Vinci/Scrapling

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

Publisher
io.github.D4Vinci
Repository
github.com/D4Vinci/Scrapling
Install
pypi:scrapling, oci:ghcr.io/d4vinci/scrapling, pypi:scrapling, pypi:scrapling, pypi:scrapling, pypi:scrapling, pypi:scrapling, pypi:scrapling
Versions
7
Inspected
4 of 6 checks · 65%
Scored
2026-07-21 · 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 clean2 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

    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.

    discloses dynamic code execution: scrapling/__init__.py: uses eval/exec/__import__ discloses dynamic code execution: scrapling/fetchers/__init__.py: uses eval/exec/__import__ discloses broad/destructive filesystem access: scrapling/spiders/result.py: open(…, 'w'/'a'/'x') write-mode file access 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.D4Vinci/[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 beacon 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.4.11 · current2026-07-12 B82.54/6 · 65%