MCP server · trust report

io.github.reesehammer/umbra-mcp

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

Publisher
io.github.reesehammer
Repository
github.com/reesehammer/umbra-py
Install
pypi:umbra-py, pypi:umbra-py, pypi:umbra-py
Versions
3
Inspected
5 of 6 checks · 75%
Scored
2026-09-07 · 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/umbra_py/dem.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 (examples/baseline/02_search_catalog_handrolled.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.1.1 (patch bump): new capability primitive(s) in source: fs-write, http-client, subprocess; new hardcoded outbound host/BCC destination(s): ..., 127.0.0.1, a.tile.openstreetmap.org, api.anthropic.com, api.canopy.umbra.space, api.openai.com, api.stacspec.org, cdn.proj.org, copernicus-dem-30m.s3.amazonaws.com, docs.canopy.umbra.space, docs.protomaps.com, ex, example, example.com, gateway.example, geotiffjs.github.io, github.com, llmstxt.org, nominatim.openstreetmap.org, nominatim.org, openrouter.ai, other.example.com, proxy.example, pypi.org, raw.githubusercontent.com, registry.npmjs.org, registry.opendata.aws, s, s3., s3.amazonaws.com, s3.us-west-2.amazonaws.com, stac-geoparquet.org, static.modelcontextprotocol.io, testserver, tile.openstreetmap.org, umbra-open-data-catalog.s3.amazonaws.com, umbra-py.space, umbra.space, unpkg.com, www.opengis.net, www.w3.org, x, x.s3.amazonaws.com.

  • Transport config

    warn10% of grade

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

    sends telemetry to third-party SDK (amplitude) — disclosure, verify opt-in; 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.2 · current2026-09-02 C605/6 · 75%B→C in v0.1.2
v0.1.12026-08-21 B753/6 · 55%—