Resource-scan receipts

peng-shawn/mermaid-mcp-server

Canonical URL: https://github.com/peng-shawn/mermaid-mcp-server · Fetched from: https://raw.githubusercontent.com/peng-shawn/mermaid-mcp-server/HEAD/README.md · Machine form: /v1/resource-scans/github-com-peng-shawn-mermaid-mcp-server-d7267ab3f4 · Markdown

Latest receipt: 3 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: 76e74ba2afa6b7c4359eeda9e652c1a1e66420b767d35b69c71c124de54c53a2 · 8341 bytes · scanned 2026-10-27T12:23:35.343Z · scanner resource-scan-v1 · ledger entry 1611.

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: glama.ai, modelcontextprotocol.io, smithery.ai. 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: glama.ai; domain: modelcontextprotocol.io; domain: smithery.ai

• 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). 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)

• 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: peng-shawn/mermaid-mcp-server; bytes scanned: 8341; fetched from: https://raw.githubusercontent.com/peng-shawn/mermaid-mcp-server/HEAD/README.md.

  Evidence: source host: github.com; repository: peng-shawn/mermaid-mcp-server; bytes scanned: 8341; fetched from: https://raw.githubusercontent.com/peng-shawn/mermaid-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 — 3 of 8 checks flagged · SHA-256 76e74ba2afa6b7c4… · 8341 bytes · scanner resource-scan-v1 · ledger entry 1611