Resource-scan receipts

SaseQ/discord-mcp

Canonical URL: https://github.com/SaseQ/discord-mcp · Fetched from: https://raw.githubusercontent.com/SaseQ/discord-mcp/HEAD/README.md · Machine form: /v1/resource-scans/github-com-saseq-discord-mcp-b711210b94 · Markdown

Latest receipt: 4 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: cc2d25b0eb08a4d5a6de778e1e2a5d9547b5082b75eba856623f3268d7c10ff8 · 16381 bytes · scanned 2026-10-27T12:23:12.419Z · scanner resource-scan-v1 · ledger entry 1598.

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: badge.mcpx.dev, discord.gg, discordjs.guide, docs.cursor.com, github.com, img.shields.io, jda.wiki, modelcontextprotocol.io, www.baeldung.com, www.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: badge.mcpx.dev; domain: discord.gg; domain: discordjs.guide; domain: docs.cursor.com; domain: github.com; domain: img.shields.io; domain: jda.wiki; domain: modelcontextprotocol.io; domain: www.baeldung.com; domain: www.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); credential file paths (.env, .ssh, credential stores). 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); credential file paths (.env, .ssh, credential stores)

• 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: SaseQ/discord-mcp; bytes scanned: 16381; fetched from: https://raw.githubusercontent.com/SaseQ/discord-mcp/HEAD/README.md.

  Evidence: source host: github.com; repository: SaseQ/discord-mcp; bytes scanned: 16381; fetched from: https://raw.githubusercontent.com/SaseQ/discord-mcp/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 cc2d25b0eb08a4d5… · 16381 bytes · scanner resource-scan-v1 · ledger entry 1598