MCP server · trust report

com.energyaisolution/energyai

3 checks that ran failed — credential hygiene, version behavior and transport config — so this release can’t be trusted as-is.

Publisher
com.energyaisolution
Repository
github.com/jdhart81/energyai-mcp
Install
remote only
Versions
11
MCP revision
2025-11-25 · superseded
Inspected
5 of 6 checks · 85%
Scored
2026-09-04 · 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 clean4 flagged1 not inspected
  • Injection surface

    warn25% of grade

    Tool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).

    tool "get_builder_upgrade_link" description: bare 'IMPORTANT:' prose in a description (tag form is high-confidence; prose is warn). tool "find_local_installers" description: bare 'IMPORTANT:' prose in a description (tag form is high-confidence; prose is warn).

  • Supply chain

    pass25% of grade

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

    repository linkage verified

  • Credential hygiene

    fail15% of grade

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

    tool "run_power_screen" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "run_power_screen" has a secret-shaped input parameter "quoteToken" — secrets must never be tool parameters (the model would supply/handle the credential). tool "bootstrap_energy_project" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "review_installer_quote" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential).

  • Permission scope

    unscannable15% of grade

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

    No source files, package.json, or pyproject were fetched; cannot infer capability scope.

  • 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 1.0.3 (patch bump): tool "get_quote_link" description changed (wording only, no injection pattern); tool "route_lead" description changed (wording only, no injection pattern); tool "create_builder_key" description changed (wording only, no injection pattern); tool "get_builder_upgrade_link" description changed (wording only, no injection pattern); new tool "get_power_passport_link" touches a sensitive surface (email/exec/net/fs); new tool "get_power_service_quote" touches a sensitive surface (email/exec/net/fs); new tool "run_power_screen" touches a sensitive surface (email/exec/net/fs).

  • Transport config

    fail10% of grade

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

    remote MCP endpoint declares NO authentication (unauthenticated remote — nginx-ui/CVE-2026-33032 class)

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.0.4 · current2026-08-16 D52.55/6 · 85%C→D in v1.0.4
v1.0.32026-08-12 C62.54/6 · 75%D→C in v1.0.3
v1.0.22026-08-09 D52.55/6 · 85%B→D in v1.0.2
v1.0.02026-07-29 B77.54/6 · 75%C→B in v1.0.0
v0.6.02026-07-27 C72.55/6 · 85%B→C in v0.6.0
v0.5.02026-07-08 B904/6 · 75%