Resource-scan receipts

pab1it0/prometheus-mcp-server

Canonical URL: https://github.com/pab1it0/prometheus-mcp-server · Fetched from: https://raw.githubusercontent.com/pab1it0/prometheus-mcp-server/HEAD/README.md · Machine form: /v1/resource-scans/github-com-pab1it0-prometheus-mcp-server-d4fe0afc1f · Markdown

Latest receipt: 5 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: b233753bc36346b54c152fe22e946e2064ac8a3fddb19ecbd72e5c98a8369580 · 8801 bytes · scanned 2026-10-27T12:23:28.405Z · scanner resource-scan-v1 · ledger entry 1607.

Analysis is static only: the bytes were read as text and were never executed, installed or run. Nothing was fetched from behind a login.

Checks (latest receipt)

• Outbound network references — flag

  The scanned bytes reference outbound network activity to these domains: astral.sh, codecov.io, github.com, hub.docker.com, img.shields.io, modelcontextprotocol.io, open.docker.com. Any resource that reaches the network can send data out as well as bring data in; the findings name what the bytes reference, and the reader decides whether that fits the resource's stated purpose.

  Evidence: domain: astral.sh; domain: codecov.io; domain: github.com; domain: hub.docker.com; domain: img.shields.io; domain: modelcontextprotocol.io; domain: open.docker.com

• Credential and environment access — flag

  The scanned bytes contain credential or environment access patterns: secret-named variables (API_KEY, SECRET, TOKEN, PASSWORD and similar names). The receipt names the pattern kinds only; no credential value is reproduced here.

  Evidence: secret-named variables (API_KEY, SECRET, TOKEN, PASSWORD and similar names)

• Install and postinstall hooks — pass

  No install or postinstall hooks were found in the scanned bytes.

• Obfuscation and encoded payloads — pass

  No obfuscation or encoded-payload signs were found in the scanned bytes.

• Shell-outs and download-and-execute — flag

  The scanned bytes contain shell-out or download patterns: shell command tools named in the bytes (curl, wget, powershell); download-and-execute pattern (fetched content passed to an executor in the same file). Code that runs shell commands acts with the full permissions of whoever runs it.

  Evidence: shell command tools named in the bytes (curl, wget, powershell); download-and-execute pattern (fetched content passed to an executor in the same file)

• Permission declarations vs behavior — flag

  The bytes show network, credentials behavior, and no permissions declaration was found in the scanned bytes to compare it against.

  Evidence: behavior: network; behavior: credentials

• Known-bad indicators — flag

  The scanned bytes match these known-bad indicators from the scanner's published pattern list: pipe-to-shell: a download piped straight into a shell interpreter. Each match is a reproducible pattern match on the bytes named by the hash; re-running the published check on the same bytes reaches the same finding.

  Evidence: pipe-to-shell: a download piped straight into a shell interpreter

• Provenance facts (weak signals) — pass

  Provenance facts, labeled weak signals — they say where the bytes sit, not what the bytes do: source host: github.com; repository: pab1it0/prometheus-mcp-server; bytes scanned: 8801; fetched from: https://raw.githubusercontent.com/pab1it0/prometheus-mcp-server/HEAD/README.md.

  Evidence: source host: github.com; repository: pab1it0/prometheus-mcp-server; bytes scanned: 8801; fetched from: https://raw.githubusercontent.com/pab1it0/prometheus-mcp-server/HEAD/README.md

History

Every receipt for this artifact so far names the same SHA-256: the bytes have not changed between scans.

• 2026-10-27 — 5 of 8 checks flagged · SHA-256 b233753bc36346b5… · 8801 bytes · scanner resource-scan-v1 · ledger entry 1607