Device scan - Oriant

The agent scans its machine on a schedule and sends a snapshot of what it finds. Each snapshot replaces the last one. You see it on the machine’s page under Assets.

What the scan finds

Finding	Example
Installed AI clients and agents	Claude Desktop, Claude Code, Cursor, found by app, config folder or running process
MCP servers in their configs	A Linear server in Cursor’s config, including Claude Desktop Extensions, with the address each one connects to
Skills	A `deploy-helper` Skill in `~/.claude/skills`, with its source. See Skills scanning
AI credentials present	That an AI provider’s API key is set, never the key itself
Agent autonomy settings	Claude Code’s permission mode, approval policies, hooks, and allow and deny lists

The scan reports names, paths and setting values only. It never sends secret values, and the only file contents it sends are the files of a Skill, so Oriant can scan them.

MCP coverage

Oriant compares the MCP servers found on machines with your MCP Connections. Each declared server is one of:

Through Oriant: it points at an Oriant connection, so its calls are checked and recorded.
Direct: it connects straight to a remote server, skipping Oriant.
Local: it runs on the machine.
Unknown: the agent reported no address.

The Coverage tab on the MCP Connections page counts the servers that don’t go through Oriant, and who has them. That is the list to move behind the gateway.

Last modified on November 11, 2026