← Registry tracker

Automox

The official Automox MCP server, packaged as a Claude Desktop Extension. Connects Claude to your Automox environment so you can manage devices, check compliance posture, run policies, prepare for Patch Tuesday, browse the worklet catalog, drive Splashtop remote-control sessions, and more — all by asking. Exposes 133 MCP tools across 18 domains (devices, policies, patches, groups, webhooks, worklets, vulnerability sync, audit, reports, Splashtop remote control, and more), 14 MCP resources (including interactive MCP App UIs for compliance triage, patch-approval review, policy blast-radius review, remediation-apply review, and RBAC access certification), and 6 workflow prompts (audit_policy, investigate_device, onboard_group, patch_tuesday, security_posture, triage_failure). Read-only mode and modular tool loading are supported via optional configuration.

View in the Claude registry
Integration type
Connector
Verification status
Verified connector
Platform
Claude
Category
Security

The broad Category that contains the Primary Subcategory.

Primary Subcategory
Pending

The Primary Subcategory used for this profile’s headline score.

Secondary Subcategories
None listed

Other Subcategories where the Integration is visible.

Brand
Automox
Access
Unknown
First tracked
2026-08-12
Tool count
133
Geography
US

Claude Discoverability Score

Your public score is being prepared

Automox is tracked in the public registry. Its Discoverability Score will appear as soon as the public benchmark is ready - never as an estimate.

Get your Discoverability Score
Primary Subcategory

Competitive lineup

No Primary Subcategory assigned yetOnce Automox has a Primary Subcategory, the Plugins and Connectors it competes with will appear here with their scores.
Score explained

How the Discoverability Score works

The Claude Discoverability Score will be the percentage of contested conversations where Automox appears in the connector picker or Claude invokes it directly. Found and Positioned will be shown as diagnostics, not score inputs.

InvisibleBuriedEmergingCompetitiveWinning

Organic discovery scoring is pending. Your Connector score will appear on this scale when measurement goes live.

FoundDiagnostic

Whether Claude found your Connector in connector search. It must be Found before it can reach the picker, but the score counts picker appearances—not search results.

PickedMain score

How often your Connector appeared in the picker, or Claude invoked it directly, across contested conversations. This percentage is the Discoverability Score; the headline number is rounded.

PositionedDiagnostic

What position your Connector appeared in when it was shown in the picker. This shows prominence, but it does not affect the score.

Read the full scoring methodologyRecommended guideHow to get your Claude Connector organically discoveredFollow the practical steps agents use to find, shortlist, and choose your Connector.
Tools

133 tools agents can invoke

Automox FAQ
How do I improve a Verified connector's discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.