Shadow AI is spreading.
You don't have to block it.

Discover, classify, and apply policy to AI agents, MCP servers, extensions, skills, plugins, hooks, CLIs, and whatever comes next.

Request Early Access

anomity - fleet dashboard

0 AI Agents

0 MCP Servers

0 Extensions

0 Skills & Plugins

0 Secrets

0 Findings

! dev-macbook-14 plaintext secret in ~/.claude/settings.json 2m

⚠ eng-laptop-07 unvetted MCP server mcp-sqlite-cloud 5m

⚠ data-mac-22 Cursor extension tabnine.tabnine-vscode not on allowlist 9m

→ design-mac-03 custom skill auto-deploy loaded into Claude Code 14m

✓ ops-laptop-22 hook PreToolUse matches policy 21m

The pain

Shadow AI is already on every managed endpoint.

AI tools arrived faster than the security program was designed to cope with. Most teams cannot answer the simplest question about any of it.

Ungoverned AI agents.
Claude, ChatGPT, Cursor, Copilot, Cline, Windsurf, and peers. Each has its own permission model. None of them report to you.
The surface attached to every agent.
Plugins, skills, hooks, CLIs, IDE extensions. Each loads into an agent and carries its own permissions. Nothing is inventoried.
Unknown MCP servers.
Wired in from public registries. They run with filesystem, shell, and network access, and are never reviewed.
Secrets in plaintext.
API keys, database URLs, JWTs, private keys. Sitting in config files any loaded agent or plugin can read.
Blanket permission grants.
Rules like Bash(*) or Write(*) hand the machine over to whatever prompt is running.
No change history.
"What was installed or modified on this machine last Thursday?" is a forensics engagement, not a query.

What Anomity surfaces

One live governance layer for AI on your fleet.

Every AI tool, extension, skill, plugin, MCP, and secret on every managed endpoint - plus the policy controls to govern them.

AI Agents

Claude, ChatGPT, Cursor, Copilot, Gemini, Cline, and peers - grouped by device and vendor.

MCP Servers

Classified as official, community, or unknown - with the capabilities each one grants.

Extensions

Every AI-related extension across VS Code, Cursor, JetBrains, and peers.

Skills

Custom skill packs loaded into agents, with the instructions they carry into every session.

Plugins

Third-party plugins extending agent behavior - including the ones nobody told you about.

Secrets

API keys, database URLs, JWTs, private keys - redacted on the endpoint before they leave the machine.

Hooks

Pre-prompt, post-tool, and event hooks - with the script each one runs and when it fires.

CLIs

AI-enabled command-line tools, wrappers, and shims that invoke agents outside the IDE.

Coverage expands as the ecosystem does. New AI artifact types are added as they emerge - the product grows with the threat surface.

What it does for you

Visibility, governance, and proof. In that order.

You don't need another dashboard. You need three specific outcomes.

A single source of truth for AI on your fleet.

One screen, updated in real time as employees install, configure, and change things. The spreadsheet nobody can keep current becomes obsolete.

Governance, not just visibility.

Define rules - no blanket Bash(*), only approved MCPs, no plaintext secrets - and policies evaluate continuously. Violations route to SIEM, Slack, email, and Jira where your team already works.

An answer when something goes wrong.

A 90-day audit trail of every added, removed, or modified MCP, permission, extension, plugin, skill, and hook. "What changed last Thursday?" becomes a single query, not a forensics engagement.

Discovery engine

Lightweight Daemon. Deep Discovery.

Deep discovery

Catalog of numerous AI tools that grows with the ecosystem.
One-pass inventory of every AI artifact type.
Multi-signal trust classifier - vendor, command, fingerprint.
Capability inference - filesystem, shell, network, credentials.
Dangerous-combination detection across capability sets.
Real-time change detection on every endpoint.

Trust by design

SOC 2 Type II attested.
Secrets stay on the endpoint.
Strict tenant isolation at the query layer.
Per-device credentials, bcrypt at rest.
Metadata only. Not source, not prompts.
90-day audit retention, longer on request.

Why now

Where Anomity fits alongside what you already run.

Anomity covers a category your existing stack was not designed for. It complements what you have, it does not replace it.

Tool class	What it sees	What Anomity covers that it misses
Network layer Gateway / Firewall / Proxy	Traffic between agents and LLM providers on the wire.	The local side: MCPs, permissions, extensions, plugins, skills, hooks, and secrets on the employee's machine. Network tools see partial AI threats at the edge; Anomity covers the endpoint.
EDR / XDR	Processes, binaries, and syscalls on the endpoint.	MCP server configuration, agent permission grants, plugin and extension inventory. An MCP server is a legitimate process doing exactly what its config allows.
DLP	File transfers and content leaving the endpoint.	The permission grants and MCP wiring that enable the transfer in the first place.
GRC / manual audit	Point-in-time snapshots captured by hand, quarterly at best.	Live fleet state, continuous enforcement, real-time change detection, a queryable audit trail.

Shadow AI is spreading. You don't have to block it.