MCP server · trust report

io.github.xfloukiex-lab/magpie-search

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

Publisher
io.github.xfloukiex-lab
Repository
github.com/xfloukiex-lab/magpie-search
Install
pypi:magpie-search
Versions
1
Inspected
4 of 6 checks · 65%
Scored
2026-07-20 · 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

    fail15% of grade

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

    src/magpie_search/redactor.py: contains a hardcoded OpenAI API key (sk-f…23 (len 28)). tests/test_redactor.py: embeds a PRIVATE KEY block. (in an example/sample file — lower severity, but a real key here still leaks.) tests/test_redactor.py: contains a hardcoded Stripe live secret key (sk_l…dc (len 32)) — in an example/sample file; verify it is not a real key. Reads secrets from the environment (e.g. src/magpie_search/backup.py) — the recommended intake shape.

  • Permission scope

    fail15% of grade

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

    HIGH: src/magpie_search/backup.py: references a sensitive credential path (/.ssh/) — the tool-poisoning exfiltration target. HIGH: shell/exec capability AND network egress together — download-and-execute risk (src/magpie_search/backup.py: subprocess.* call; src/magpie_search/deepweb.py: outbound HTTP/socket call). HIGH: shell/exec capability AND destructive filesystem writes together (src/magpie_search/backup.py: subprocess.* call; src/magpie_search/indexer.py: path traversal ('../') combined with file access). discloses shell/exec capability: src/magpie_search/backup.py: subprocess.* call discloses shell/exec capability: src/magpie_search/safe_subprocess.py: subprocess.* call discloses dynamic code execution: tests/test_backup_hardening.py: uses eval/exec/__import__ discloses broad/destructive filesystem access: src/magpie_search/indexer.py: path traversal ('../') combined with file access discloses broad/destructive filesystem access: tests/test_indexer_robustness.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.xfloukiex-lab/[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

    warn10% of grade

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

    manifest/source references Heartbeat 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
v1.2.1 · current2026-06-18 C654/6 · 65%