Resource-scan receipts

mcp-use/mcp-use

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

Latest receipt: 2 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: 278f2f9b00237ecdafa9282fce21c60126c6d889d631c420f030f60a2cc6bd1d · 16828 bytes · scanned 2026-10-27T12:18:48.246Z · scanner resource-scan-v1 · ledger entry 1504.

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: contrib.rocks, dcbadge.limes.pink, discord.gg, docs.mcp-use.com, gist.githubusercontent.com, github.com, img.shields.io, inspector.mcp-use.com, lucky-darkness-402ph.run.mcp-use.com, manufact.com, mcp-use.com, pypi.org, raw.githubusercontent.com, super-night-ttde2.run.mcp-use.com, www.npmjs.com, yellow-shadow-21833.run.mcp-use.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: contrib.rocks; domain: dcbadge.limes.pink; domain: discord.gg; domain: docs.mcp-use.com; domain: gist.githubusercontent.com; domain: github.com; domain: img.shields.io; domain: inspector.mcp-use.com; domain: lucky-darkness-402ph.run.mcp-use.com; domain: manufact.com; domain: mcp-use.com; domain: pypi.org; domain: raw.githubusercontent.com; domain: super-night-ttde2.run.mcp-use.com; domain: www.npmjs.com; domain: yellow-shadow-21833.run.mcp-use.com

• Credential and environment access — pass

  No credential or environment access patterns were found in the scanned bytes.

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

  No shell-out or download-and-execute patterns were found in the scanned bytes.

• Permission declarations vs behavior — flag

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

  Evidence: behavior: network

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

  Evidence: source host: github.com; repository: mcp-use/mcp-use; bytes scanned: 16828; fetched from: https://raw.githubusercontent.com/mcp-use/mcp-use/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 — 2 of 8 checks flagged · SHA-256 278f2f9b00237ecd… · 16828 bytes · scanner resource-scan-v1 · ledger entry 1504