Resource-scan receipts

exa-labs/exa-mcp-server

Canonical URL: https://github.com/exa-labs/exa-mcp-server · Fetched from: https://raw.githubusercontent.com/exa-labs/exa-mcp-server/HEAD/README.md · Machine form: /v1/resource-scans/github-com-exa-labs-exa-mcp-server-084da3f431 · Markdown

Latest receipt: 4 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: 08a2ffb7efbfd07dbadac74435f8cabb2a265cc3389dfcc4a3303b42c21a934f · 7653 bytes · scanned 2026-10-27T12:21:20.152Z · scanner resource-scan-v1 · ledger entry 1546.

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: agent-plugins.org, chatgpt.com, claude.com, cursor.com, custom-icon-badges.demolab.com, dashboard.exa.ai, docs.exa.ai, github.com, img.shields.io, lmstudio.ai, mcp.exa.ai, replit.com, v0.app, vscode.dev, www.npmjs.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: agent-plugins.org; domain: chatgpt.com; domain: claude.com; domain: cursor.com; domain: custom-icon-badges.demolab.com; domain: dashboard.exa.ai; domain: docs.exa.ai; domain: github.com; domain: img.shields.io; domain: lmstudio.ai; domain: mcp.exa.ai; domain: replit.com; domain: v0.app; domain: vscode.dev; domain: www.npmjs.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 — flag

  The scanned bytes carry obfuscation or encoding signs: 1 long base64-shaped run (120+ characters). Encoded content cannot be read from the bytes alone, so what it does cannot be checked from the bytes alone either.

  Evidence: 1 long base64-shaped run (120+ characters)

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

  Evidence: source host: github.com; repository: exa-labs/exa-mcp-server; bytes scanned: 7653; fetched from: https://raw.githubusercontent.com/exa-labs/exa-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 — 4 of 8 checks flagged · SHA-256 08a2ffb7efbfd07d… · 7653 bytes · scanner resource-scan-v1 · ledger entry 1546