AI Discovery · Part of Orpheus

What AI is running on your machines?

AI Discovery finds every AI tool on every machine in your company, from coding agents and AI editors to desktop assistants, AI browsers, local models and MCP servers. It shows what each one can do and reach, and lets you sanction or block it for the whole team.

EVERY AI TOOL · EVERY MACHINE · EVERY HOUR — macOS, Windows & Linux, read-only
Every tool, what it can do, where it runs, whether you allow it.
01The AI you can't seeThe problem

Outside every hook and gateway

ChatGPT on the desktop, Ollama serving models, an AI browser, a sidebar extension in Chrome. None of it crosses a proxy. The only way to know it exists is to look at the machine.

Set up to act without asking

A sanctioned agent is still a risk when it skips permission checks, runs with its sandbox off, or runs from a scheduled job with no one at the keyboard.

Reach nobody mapped

MCP servers wired into production databases, credentials in home folders, packages fetched unpinned on every start. No one has written down what each agent can reach.

02Every tool, how it signs in, what it can doDiscover

A catalog of AI tools in every category, from coding agents and AI editors to desktop assistants, AI browsers, local model runtimes, SDKs, browser extensions and MCP servers. Tools the catalog has never seen still show up: model files, apps with an AI runtime inside, extensions that declare AI features.

Owner and sign-in. Who runs it and how it authenticates; a work account or a personal one.
Privileges. Runs as root, approves its own actions, sandbox off, a local API open to the network, runs unattended.
Data reach. The MCP servers wired in, the databases it can reach, the websites an extension can read.
Last validated. When the evidence was last re-verified, and whether the tool is running now.

One tool, across the fleet: who runs it, how it signs in, what it can do, what it reaches.

03How far each agent reachesRisks

An exfiltration path has three legs: the agent reads private data, takes in content outsiders can write, and can send data out. AI Discovery assembles each leg from the tool's capabilities, its MCP servers, the credentials in reach and its live connections, then asks who approves.

Exfiltration paths, ranked. Critical when the path is complete and nobody approves.
Databases in reach. Engine, provider, production or not, and how the agent gets to it.
MCP supply chain. Malicious packages, vulnerable versions and unpinned servers, each with the fix.
Unattended agents. Scheduled jobs and headless runs, and which of them skip permission checks.

Risks: a complete path with no one approving is critical. The same tool with a person at the keyboard is not.

04Sanction, block, reviewDecide

Every newly found tool waits as Unsanctioned. Allow or block it once, with a note, and the decision applies to every endpoint on the team. AI Discovery supplies the facts; Orpheus enforces.

Blocked coding agents are refused. Block Claude Code, Cursor or Codex and every action it sends through Orpheus is refused, with your note as the reason.
Everything else is flagged on every endpoint it is on.
MCP servers appear in MCP Governance before their first call, so you can authorize or deny them ahead of use.
A heartbeat every hour. A machine that stops reporting is flagged, not assumed clean.

Policy: one decision per tool, team-wide, with who decided and why.

05One command per machineHow it works
  1. 01

    Install

    One line from the Orpheus install page, on macOS, Windows or Linux. The first scan runs right away; the scanner keeps itself scheduled and up to date.

  2. 02

    Scan

    Every hour, in the background, done in seconds. It reads what is installed and how it is set up; never files, prompts or secrets.

  3. 03

    Review

    Open Orpheus to see the directory, the risks and the policy for the whole team. Decide once, and every machine follows.

What it reads

  • Which AI apps, agents, editors, extensions and local models are installed, and their versions
  • How each one is set up: the account it signs in with, whether it approves its own actions, whether it runs unattended
  • Which MCP servers, databases and services it is wired to
  • Whether a credential exists for it, and when it last changed

What it never does

  • Read or send a secret, a prompt or a file's contents
  • Run anything it finds
  • Stop, remove or change software on its own. It reads; Orpheus enforces
  • Slow anyone down. It runs in the background and is done in seconds
06Start with Cassandra. Grow into AI Discovery.Free · Then the fleet

Cassandra is the free, one-machine cut of this: it checks your extensions against 11,174 known-malicious ones, once, on the machine you run it on. AI Discovery is what a team needs after that.

Cassandra Free AI Discovery Part of Orpheus
Machines One, the one you run it on Every endpoint on the team
When Once, when you run the command Every hour, in the background
Finds Editor and browser extensions; the names of AI tools and key variables Every AI tool in the catalog, from coding agents to local models and MCP servers, plus model files, AI-embedding apps and AI extensions the catalog has never seen
Checks 11,174 known-malicious extensions, marketplace status, the traces of published attacks How each tool signs in, what it runs without asking, what it reaches, and which MCP packages are malicious, vulnerable or unpinned
Decides Tells you what to do next Sanction or block, team-wide; blocked coding agents are refused wherever Orpheus runs
Who Anyone, right now Orpheus teams, or on its own as Orpheus Discovery

See every AI tool on your fleet.

Book a 30-minute walkthrough. The first scan takes seconds; the directory fills in as machines report.