Resource-scan receipts

robotmcp/ros-mcp-server

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

Latest receipt: 2 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: b9d36be96e8a12b6a8120bb3ab4a486be7d5042ed64047f711469d7ce6163bcd · 4902 bytes · scanned 2026-10-27T12:23:38.992Z · scanner resource-scan-v1 · ledger entry 1613.

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: github.com, img.shields.io, img.youtube.com, modelcontextprotocol.io, www.traceglarue.com, www.youtube.com, youtu.be. 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: github.com; domain: img.shields.io; domain: img.youtube.com; domain: modelcontextprotocol.io; domain: www.traceglarue.com; domain: www.youtube.com; domain: youtu.be

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

  Evidence: source host: github.com; repository: robotmcp/ros-mcp-server; bytes scanned: 4902; fetched from: https://raw.githubusercontent.com/robotmcp/ros-mcp-server/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 b9d36be96e8a12b6… · 4902 bytes · scanner resource-scan-v1 · ledger entry 1613