What do you actually use?

Openwake Scout

Scout reports what a machine does: which AI tools are installed, which MCP servers are configured and where they point, which model-provider keys exist, which AI apps are running. Every finding maps onto the Registry, so you see your AI supply chain as it is, not as a paste.

Scout Agent

One small program per operating system: enrol with your organisation key, report once, then every six hours through the system scheduler (launchd, systemd or Task Scheduler), and uninstall in one command. It identifies relationships, not content.

Scout Browser Extension

The badge on every site you open says, in the vendor's own words, what that site does with your data. It sends only the tab's registrable domain and keeps a local tally that never leaves the browser.

Levels of confidence

Installed is not used. Scout says how sure it is: a desktop app on disk is medium; a browser reaching notion.so is high; the vendor's own app reaching its own API is very high.

What it never collects

Passwords, cookies, request payloads, page contents, clipboard, keystrokes, screenshots, URL paths, browsing history unrelated to monitored vendors, model output.

npx @openwake/scout --post openwake scout · device 8f2c… · darwin tools (7) Claude Code, Claude Desktop, Cursor, VS Code, Codex CLI, ChatGPT Desktop, Ollama mcp servers (6) memory, playwright, sequential-thinking, … registry match: 3 vendors on record, 4 queued Anthropic trains on customer data: opt_out Microsoft 365 trains on customer data: opt_out OpenAI trains on customer data: opt_in
The platform

Openwake Scout is one of five products on one graph: Registry, Watch, Scout, Agreements, Recorder. How they fit together.