Resource-scan receipts

elastic/mcp-server-elasticsearch

Canonical URL: https://github.com/elastic/mcp-server-elasticsearch · Fetched from: https://raw.githubusercontent.com/elastic/mcp-server-elasticsearch/HEAD/README.md · Machine form: /v1/resource-scans/github-com-elastic-mcp-server-elasticsearch-6e47eeb1dc · Markdown

Latest receipt: 4 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: 8e81dbc09d4f690aec28641c0e180eaa39fc75c276f7c3fa891252b75da4c928 · 10660 bytes · scanned 2026-10-27T12:19:18.776Z · scanner resource-scan-v1 · ledger entry 1520.

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: console.aws.amazon.com, docs.aws.amazon.com, ela.st, github.com, modelcontextprotocol.io, www.elastic.co, your-cluster.es.amazonaws.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: console.aws.amazon.com; domain: docs.aws.amazon.com; domain: ela.st; domain: github.com; domain: modelcontextprotocol.io; domain: www.elastic.co; domain: your-cluster.es.amazonaws.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); authorization headers and bearer values. 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); authorization headers and bearer values

• 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). 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)

• 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 — pass

  None of the scanner's published known-bad indicator patterns matched the scanned bytes.

• 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: elastic/mcp-server-elasticsearch; bytes scanned: 10660; fetched from: https://raw.githubusercontent.com/elastic/mcp-server-elasticsearch/HEAD/README.md.

  Evidence: source host: github.com; repository: elastic/mcp-server-elasticsearch; bytes scanned: 10660; fetched from: https://raw.githubusercontent.com/elastic/mcp-server-elasticsearch/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 — 4 of 8 checks flagged · SHA-256 8e81dbc09d4f690a… · 10660 bytes · scanner resource-scan-v1 · ledger entry 1520