Resource-scan receipts

mobile-next/mobile-mcp

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

Latest receipt: 3 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: 1da8407be9a4559f1611d47268652d2a904912ebf39e96a7a3a32ac73288909a · 24889 bytes · scanned 2026-10-27T12:21:54.281Z · scanner resource-scan-v1 · ledger entry 1564.

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: api.star-history.com, contrib.rocks, cursor.com, developer.android.com, developer.apple.com, github.com, goose-docs.ai, img.shields.io, insiders.vscode.dev, kiro.dev, mobilenext.ai, mobilewright.dev, modelcontextprotocol.io, nodejs.org, openai.github.io, opencode.ai, raw.githubusercontent.com, www.microsoft.com, www.npmjs.com, www.star-history.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: api.star-history.com; domain: contrib.rocks; domain: cursor.com; domain: developer.android.com; domain: developer.apple.com; domain: github.com; domain: goose-docs.ai; domain: img.shields.io; domain: insiders.vscode.dev; domain: kiro.dev; domain: mobilenext.ai; domain: mobilewright.dev; domain: modelcontextprotocol.io; domain: nodejs.org; domain: openai.github.io; domain: opencode.ai; domain: raw.githubusercontent.com; domain: www.microsoft.com; domain: www.npmjs.com; domain: www.star-history.com

• Credential and environment access — flag

  The scanned bytes contain credential or environment access patterns: authorization headers and bearer values. The receipt names the pattern kinds only; no credential value is reproduced here.

  Evidence: 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 — pass

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

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

  Evidence: source host: github.com; repository: mobile-next/mobile-mcp; bytes scanned: 24889; fetched from: https://raw.githubusercontent.com/mobile-next/mobile-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 — 3 of 8 checks flagged · SHA-256 1da8407be9a4559f… · 24889 bytes · scanner resource-scan-v1 · ledger entry 1564