Summary
ThreatAware cyber asset management from any AI agent: the merged device and user inventory across your security and IT tools, open alerts, the health of each security control (Vitals, today or on a past day), the raw records of one connected tool, and the portal users, roles and teams. Read-only. Cloud ID and API key.
Guided setup
Connect ThreatAware to Claude, ChatGPT or Copilot in 2 minutes
Start a free trial on AnythingMCP Cloud, connect ThreatAware in the guided setup, then add your MCP URL to your AI assistant. No code and no server to run.
No credit card · 7-day trial · Self-host alternative available
Try asking
Example prompts for ThreatAware
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → ThreatAware, paste your credentials, mint an MCP API key and you're done. No Docker, no
git clone, no local server.
ThreatAware
ThreatAware cyber asset management from any AI agent: the merged device and user inventory across your security and IT tools, open alerts, the health of each security control (Vitals, today or on a past day), the raw records of one connected tool, and the portal users, roles and teams. Read-only. Cloud ID and API key.
Setup
Setting up takes about 3 minutes.
- Sign in to your portal and note the first part of its address: for
https://acme-corp.threataware.comthe Cloud ID isacme-corp. Put it intoTHREATAWARE_CLOUD_ID. - Open Settings, API Access (address
/settings/api) and click Generate Key. Name the key, pick an expiry (1 day, 1 week, 1 month or Never; the default is 1 day, so choose on purpose) and save. - Copy the key at once (it is shown only once) into
THREATAWARE_API_KEY. It is sent in theX-ThreatAware-ApiKeyheader.
The key sees what its creator sees. ThreatAware recommends creating it under a dedicated service user with a narrow role instead of a personal account.
Where to start
threataware_list_vitalsshows every connected tool with its internal name (key) and, where Vitals is on, how many devices have the agent deployed, working and correctly configured. Read the three pairs as a funnel: deployed out of expected, functioning out of deployed, configured out of functioning.threataware_list_alertswith filterallunresolvedlists what is open now;stateRed is urgent, Amber is a warning.threataware_list_devicesis the merged device inventory.SecurityToolson a device shows the alert counts per tool,ConnectedSystemswhere the device is known.threataware_list_usersis the merged list of people, with MFA and admin flags inmetadataand the last successful and failed sign-in.threataware_list_inventoryreturns one tool's raw records when you need a field the merged lists do not have. It needs the tool's internal name, which is thekeyfromthreataware_list_vitalsand not always the name shown in the portal (Microsoft Intune isdevices_msgraph, SCCM ismecmsystem).- Portal administration:
threataware_list_portal_users,threataware_list_rolesandthreataware_list_teamsdescribe who can sign in to ThreatAware and with which rights.
Paging: every list takes offset and limit and answers total. ThreatAware returns the whole data set when no limit is sent, so this connector always sends one (100 by default). On devices and users the offset stops at 10,000 records (status 400 beyond that); narrow with filter instead.
Reading the data
- Times are ISO 8601 without a time zone, e.g.
2026-10-10T08:49:28.0000000.0001-01-01T00:00:00means "never" (not acknowledged, not resolved, not snoozed). - There are no server-side searches by host name, user or severity: fetch pages and filter the result yourself.
- Device and user data is personal data (names, emails, IP addresses, sign-in locations). Share only what the question needs.
Limits and errors: 50 requests per minute for the whole portal, whichever key is used; status 429 means wait a minute. Status 400 with "Unexpected error occurred." means the key is wrong, disabled or expired (ThreatAware answers 400, not 401, for a bad key). 401 means no key was sent. 403 means the key's user lacks the permission for that area. A portal address that does not resolve means the Cloud ID is wrong.
Prerequisites: THREATAWARE_CLOUD_ID, THREATAWARE_API_KEY
Install the connector locally
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Open http://localhost:3000/connectors/store, pick ThreatAware and paste in the env vars listed under Prerequisites.
Available tools
| Tool | What it does |
|---|---|
threataware_list_devices | List the devices ThreatAware has merged from all connected tools. Each device has id, hostName, os, osVersion, lastOnline, firstSeen… |
threataware_list_users | List the people ThreatAware has collected from the connected directories and identity providers. Each user has id, name, email, jobTitle… |
threataware_list_alerts | List the alerts (issues) ThreatAware raised across the environment. Each alert has state (Red, Amber or Green), product (tool and… |
threataware_list_inventory | Read the raw records ThreatAware holds for one connected tool, in that tool's own field names (for example Automox patch counts, or… |
threataware_list_vitals | Get the health of every connected security tool (Vitals), today or on a past day. Each entry has key (the internal tool name used by the… |
threataware_list_portal_users | List the accounts that can sign in to the ThreatAware portal itself (not the people found in the directories: for those call… |
threataware_list_roles | List the roles of the ThreatAware portal. Each role has id (for example superAdmin, analyst or viewer), name, description, default (true… |
threataware_list_teams | List the teams of the ThreatAware portal with their members. Each team has id, name and members (username, name and surname). Teams scope… |
Example prompts
- "Which security tools have the biggest gap between expected and deployed devices?"
- "List all unresolved Red alerts."
- "Which users have no MFA but admin rights?"
- "Show the devices that are missing the EDR agent."
- "Who can sign in to our ThreatAware portal, and with which roles?"
Next steps
Was this guide helpful?