argoproj-labs/mcp-for-argocd

Canonical URL: https://github.com/argoproj-labs/mcp-for-argocd · Fetched from: https://raw.githubusercontent.com/argoproj-labs/mcp-for-argocd/HEAD/README.md · Machine form: /v1/resource-scans/github-com-argoproj-labs-mcp-for-argocd-ceb695960f · Markdown

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

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: akuity.io, argo-a.example.com, argo-b.example.com, argo-cd.readthedocs.io, argo.example.com, argocd.other-cluster.example.com, code.visualstudio.com, docs.cursor.com, github.com, glama.ai, img.shields.io, insiders.vscode.dev, modelcontextprotocol.io. 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: akuity.io; domain: argo-a.example.com; domain: argo-b.example.com; domain: argo-cd.readthedocs.io; domain: argo.example.com; domain: argocd.other-cluster.example.com; domain: code.visualstudio.com; domain: docs.cursor.com; domain: github.com; domain: glama.ai; domain: img.shields.io; domain: insiders.vscode.dev; domain: modelcontextprotocol.io
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 — flag
The scanned bytes match these known-bad indicators from the scanner's published pattern list: token- or credential-taking vocabulary (stealer, grabber, exfiltrate). 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: token- or credential-taking vocabulary (stealer, grabber, exfiltrate)
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: argoproj-labs/mcp-for-argocd; bytes scanned: 24349; fetched from: https://raw.githubusercontent.com/argoproj-labs/mcp-for-argocd/HEAD/README.md.
Evidence: source host: github.com; repository: argoproj-labs/mcp-for-argocd; bytes scanned: 24349; fetched from: https://raw.githubusercontent.com/argoproj-labs/mcp-for-argocd/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 ee3085dfe71f96dc… · 24349 bytes · scanner resource-scan-v1 · ledger entry 1608