Teams · free
Fleet view
Which AI coding tools and MCP servers run on your developers' machines, which versions are below the minimum safe version, and which MCP packages have advisories. Each machine runs threatdeck scan --upload; only inventory is sent, never paths, names or config contents.
Free, no billing, up to 500 machines per fleet. Machines that have not uploaded for 30 days drop off.
Create a fleet
Fleet created
Both tokens are shown once. The admin token opens this dashboard (it is also kept in this browser). The upload token can only add machine inventory: put it on developer machines or in CI secrets.
- Admin token
- Upload token
On a developer machine
Needs Node.js 22.12 or later. The scanner is one file downloaded from this site; see threatdeck scan for checksum verification.
MDM (Jamf, Kandji, Intune) weekly script
Run it as the signed-in user, not root, so the scan sees that user's tools and MCP configs. Use a team name as the label, not a username or hostname.
GitHub Actions (repo MCP configs)
Store the upload token as the THREATDECK_FLEET_TOKEN secret. The cache keeps one machine id per repository instead of one per run.
Dashboard
ThreatDeck fleet brief · AI coding tools and MCP servers across your developer machines · generated from the latest uploads. Versions are checked against published minimum safe versions; MCP packages against OSV/GitHub advisories. Details: threatdeck.net/fleet/
Alert keys are devtool-… and pkg:… follow keys for every tool and MCP package in the fleet. Paste them into a team alert channel to hear about new advisories (the free plan follows up to 15).
AI coding tools
checked against the minimum safe versions| Tool | Machines | Below minimum safe | Minimum safe | Versions in use |
|---|
MCP packages
advisories from MCP Server Watch, matched to the versions in use| Package | Machines | Affected machines | Advisories | Versions in use |
|---|
An unpinned install (no version) may run any release, so it counts as affected by every advisory for that package.
Machines
labels are whatever each machine passed to--label| Label | OS | Last seen | Tools | MCP | Below min. safe | Package advisories | Findings |
|---|
Remote MCP hosts
public hosts only| Host | Machines |
|---|
Exactly what a machine uploads
Only with --upload <token> or THREATDECK_FLEET_TOKEN; --offline forbids it. The CLI prints one line saying what it sent, and the server rejects any upload with a field outside this list.
- A random machine id, created once at
~/.config/threatdeck/machine-id(not derived from the hostname, MAC address or username; stored on the server only as a hash). - Your
--label(optional, up to 60 characters), the CLI version and the OS family (macOS, Linux or Windows). - AI coding tool slugs and versions, e.g.
claude-code 2.1.319. - For each enabled MCP server: the client, the transport, the package id (
npm:@scope/server@1.2.3) when the scanner would already send it to the lookup API, and the remote host only when it is public. - Finding counts by rule id and severity (for example 2 ×
TD-MCP-UNPINNEDlow), never finding text.
Never sent: file paths, usernames, hostnames, server names, commands, arguments, env or header names and values, config contents, transcripts.