MCP server · trust report

io.github.Sahil170595/chimeraforge

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

Publisher
io.github.Sahil170595
Repository
github.com/Sahil170595/Chimeraforge
Install
pypi:chimeraforge, pypi:chimeraforge, pypi:chimeraforge, pypi:chimeraforge, pypi:chimeraforge, pypi:chimeraforge, pypi:chimeraforge, pypi:chimeraforge, pypi:chimeraforge, pypi:chimeraforge, pypi:chimeraforge, pypi:chimeraforge, pypi:chimeraforge, pypi:chimeraforge, pypi:chimeraforge, pypi:chimeraforge, pypi:chimeraforge, pypi:chimeraforge, pypi:chimeraforge, pypi:chimeraforge, pypi:chimeraforge, pypi:chimeraforge, pypi:chimeraforge, pypi:chimeraforge, pypi:chimeraforge, pypi:chimeraforge, pypi:chimeraforge, pypi:chimeraforge, pypi:chimeraforge
Versions
29
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

    fail25% of grade

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

    Python build script executes at build time: network call in build script

  • 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. src/chimeraforge/planner/resolver.py) — the recommended intake shape. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.

  • Permission scope

    pass15% of grade

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

    Network egress present (src/chimeraforge/bench/backends/ollama.py: outbound HTTP/socket call) — expected for most servers and not a finding on its own. No shell-exec, unbounded/sensitive filesystem, or download-and-run primitives found in scanned source. PASS = no static red flag. Static scanning is blind to code fetched or executed at runtime.

  • 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.30.1 (patch bump): new capability primitive(s) in source: fs-write, http-client; new hardcoded outbound host/BCC destination(s): chimeraforge.vercel.app, github.com, gpu-server, huggingface.co, 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 usage stats 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.30.9 · current2026-08-29 C605/6 · 75%B→C in v0.30.9
v0.30.12026-08-26 B754/6 · 65%±0
v0.30.02026-08-22 B754/6 · 65%±0
v0.22.12026-08-21 B754/6 · 65%±0
v0.21.02026-08-19 B753/6 · 55%C→B in v0.21.0
v0.19.02026-08-18 C705/6 · 75%±0
v0.14.02026-08-15 C705/6 · 75%±0
v0.13.02026-08-14 C705/6 · 75%±0
v0.12.32026-08-12 C704/6 · 65%