# Teramind (oci · ghcr.io/wyre-ai/teramind-mcp:v1.0.0) MCP server for Teramind's insider-threat/employee-monitoring API (read-only, metadata-only surface). - Trust score: 39/100 (low) - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-09-20 ## Components - oci · `ghcr.io/wyre-ai/teramind-mcp:v1.0.0`: 39/100 (this document), [markdown](https://verifymcp.io/servers/wyre-ai-teramind-mcp/ghcr-io-wyre-ai-teramind-mcp-v1-0-0.md), [page](https://verifymcp.io/servers/wyre-ai-teramind-mcp/ghcr-io-wyre-ai-teramind-mcp-v1-0-0) ## Channel facts - Registry: `oci` - Package: `ghcr.io/wyre-ai/teramind-mcp:v1.0.0` - Transport: `stdio` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-09-20. - **Supply Chain Security**: 0/100 - Malware scan not yet available for this package. - Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it. - Install-script risk not yet assessed. - Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it. - **Provenance & Transparency**: 32/100 - Source repository is publicly reachable at the declared URL. - Provenance check failed: no build-provenance attestation is published. - License check failed: the license (NOASSERTION) isn't a recognized OSI-approved license. - Actively maintained (last published 0 days ago). - Disclosure check failed: no security disclosure policy was found in the source repository. - **Schema Quality & AI Usability**: 80/100 - AI-judged instruction clarity (excellent). - Tool/resource definitions use about 1235 tokens (~77/item across 16 items; 16 tools + 0 resources), lean. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 0/100 - Stability not yet verified: not enough scan history yet (needs a 30-day window). - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. **Unverified: 2 categories.** Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm. ## Install ### How do I install the Teramind MCP server? Teramind runs locally as a container image, launched with docker run --rm -i ghcr.io/wyre-ai/teramind-mcp:v1.0.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add wyre-ai-teramind-mcp -- docker run --rm -i ghcr.io/wyre-ai/teramind-mcp:v1.0.0 ``` ### Cursor ```json { "mcpServers": { "wyre-ai-teramind-mcp": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/wyre-ai/teramind-mcp:v1.0.0" ] } } } ``` ### VS Code ```json { "servers": { "wyre-ai-teramind-mcp": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/wyre-ai/teramind-mcp:v1.0.0" ] } } } ``` ### Codex ```bash codex mcp add wyre-ai-teramind-mcp -- docker run --rm -i ghcr.io/wyre-ai/teramind-mcp:v1.0.0 ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "wyre-ai-teramind-mcp": { "type": "local", "command": [ "docker", "run", "--rm", "-i", "ghcr.io/wyre-ai/teramind-mcp:v1.0.0" ], "enabled": true } } } ``` ### Hermes ```yaml mcp_servers: wyre-ai-teramind-mcp: command: "docker" args: ["run", "--rm", "-i", "ghcr.io/wyre-ai/teramind-mcp:v1.0.0"] ``` ### Netclaw ```json { "McpServers": { "wyre-ai-teramind-mcp": { "Transport": "stdio", "Command": "docker", "Arguments": [ "run", "--rm", "-i", "ghcr.io/wyre-ai/teramind-mcp:v1.0.0" ] } } } ``` ### Other ```json { "mcpServers": { "wyre-ai-teramind-mcp": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/wyre-ai/teramind-mcp:v1.0.0" ] } } } ``` ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-09-20 (score 39) First indexed and scored. ## MCP tools (16) ### `teramind_list_computers` (~75 tokens) List computers under Teramind monitoring - hostname, FQDN, MAC/IP addresses, OS, monitoring status (is_monitored), and agent-software install/update state. Computer IDs from this response are required by teramind_get_computer. Inventory metadata only - never screen recordings or captured activity content. ### `teramind_get_computer` (~53 tokens) Get full detail for a single monitored computer. Requires a computer ID from teramind_list_computers. Input parameters: - `computer_id` (string, required): Computer ID, from teramind_list_computers. ### `teramind_list_agents` (~107 tokens) List Teramind agents (Teramind's term for a monitored employee/user identity - not the software agent installed on a computer): id, name, email, avatar, online status. Agent IDs from this response are required by teramind_get_agent and are usable as filters on teramind_list_alerts. This connector never requests the underlying API's optional extended fields (salary_type, default_wage, ldap_attrs) - only these basic identity fields are ever returned. ### `teramind_get_agent` (~67 tokens) Get full detail for a single monitored agent (user). Requires an agent ID from teramind_list_agents. Same field restriction as teramind_list_agents - no compensation or LDAP attribute data. Input parameters: - `agent_id` (string, required): Agent ID, from teramind_list_agents. ### `teramind_list_departments` (~49 tokens) List departments configured in Teramind - org-structure metadata used to group agents/computers. Department IDs from this response are usable as filters on teramind_list_alerts. ### `teramind_get_department` (~49 tokens) Get full detail for a single department. Requires a department ID from teramind_list_departments. Input parameters: - `department_id` (string, required): Department ID, from teramind_list_departments. ### `teramind_list_alerts` (~282 tokens) List alerts (fired rule-violation events) in a time window - which rule fired, when, for which agent/computer, and the rule's own description/caption fields. periodStart and periodEnd are required (ISO 8601 datetime, e.g. 2026-01-01T00:00:00Z); optionally scope to specific agents/computers/departments (comma-separated IDs). NOTE: depending on the rule type that fired, a rule's description/caption/values fields MAY include a short excerpt of the triggering context (e.g. a matched keyword or URL) rather than pure metadata - this is Teramind's documented alert response shape, passed through as received. Input parameters: - `agents` (string): Comma-separated agent IDs to filter by. From teramind_list_agents. - `computers` (string): Comma-separated computer IDs to filter by. From teramind_list_computers. - `departments` (string): Comma-separated department IDs to filter by. From teramind_list_departments. - `limit` (number): Max results. Defaults to 50. - `offset` (number): Pagination offset. Defaults to 0. - `periodEnd` (string, required): ISO datetime, inclusive upper bound. - `periodStart` (string, required): ISO datetime, inclusive lower bound. ### `teramind_list_anomaly_rules` (~88 tokens) List configured ML-based anomaly-detection rules (Teramind UI: "Anomaly Rules") - rule name, type/subtype, risk quotient, trigger conditions, and assignment scope. Rule CONFIGURATION metadata only - describes what is being watched for, never the captured activity that triggered a rule. Rule IDs from this response are required by teramind_get_anomaly_rule. ### `teramind_get_anomaly_rule` (~55 tokens) Get full detail for a single anomaly rule. Requires a rule ID from teramind_list_anomaly_rules. Input parameters: - `id` (string, required): Anomaly rule ID, from teramind_list_anomaly_rules. ### `teramind_list_anomaly_rule_tags` (~23 tokens) List the tags available to categorize anomaly rules. ### `teramind_list_behavior_policies` (~89 tokens) List behavior policies (Teramind UI: "behavior policy rule") - what activity type each policy watches (e.g. web/email/print), its match conditions, and configured actions/reactions. Rule CONFIGURATION metadata only - the condition a policy matches on, never the captured activity that matched it. Policy IDs from this response are required by teramind_get_behavior_policy. ### `teramind_get_behavior_policy` (~53 tokens) Get full detail for a single behavior policy. Requires a policy ID from teramind_list_behavior_policies. Input parameters: - `id` (string, required): Behavior policy ID, from teramind_list_behavior_policies. ### `teramind_list_behavior_policy_groups` (~51 tokens) List behavior policy groups (Teramind UI: "Behavior policy") - the containers that organize behavior policies. Group IDs from this response are required by teramind_get_behavior_policy_group. ### `teramind_get_behavior_policy_group` (~56 tokens) Get full detail for a single behavior policy group. Requires a group ID from teramind_list_behavior_policy_groups. Input parameters: - `id` (string, required): Behavior policy group ID, from teramind_list_behavior_policy_groups. ### `teramind_list_monitoring_profiles` (~77 tokens) List monitoring profiles - named configurations describing WHICH data types are captured (e.g. web activity, email, keystrokes) and for which agents, plus whether the profile is private. This is metadata ABOUT the scope of monitoring (what is configured to be watched, and for whom) - never the captured content itself. ### `teramind_get_account` (~61 tokens) Get the authenticated account's own settings (account name, timezone, currency) - a credential sanity check, not employee/agent data. Does not reveal what permission tier the access token's creating account holds; see this connector's README Credential scope section. ## Diagnostics Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/wyre-ai-teramind-mcp/ghcr-io-wyre-ai-teramind-mcp-v1-0-0#diagnostics ## Score history - 2026-09-20: 39 ## Common questions ### What is the Teramind MCP server? Teramind is an MCP server listed in the public MCP registry as io.github.WYRE-AI/teramind-mcp. MCP server for Teramind's insider-threat/employee-monitoring API (read-only, metadata-only surface). This page covers its container image (ghcr.io/wyre-ai/teramind-mcp:v1.0.0). ### Is the Teramind MCP server safe to use? Teramind scores 39 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm. ### What tools does the Teramind MCP server expose? Teramind exposes 16 tools: teramind_list_computers, teramind_get_computer, teramind_list_agents, teramind_get_agent, teramind_list_departments, and 11 more. Their descriptions and schemas cost roughly 1,235 tokens of context every time the server is loaded. ### Is the Teramind MCP server still maintained? Teramind is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ### What licence is the Teramind MCP server under? Teramind declares the NOASSERTION licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls. ## Links - Repository: https://github.com/WYRE-AI/teramind-mcp - Changelog RSS feed: https://verifymcp.io/servers/wyre-ai-teramind-mcp/ghcr-io-wyre-ai-teramind-mcp-v1-0-0.xml - Changelog JSON feed: https://verifymcp.io/servers/wyre-ai-teramind-mcp/ghcr-io-wyre-ai-teramind-mcp-v1-0-0.json - HTML version of this page: https://verifymcp.io/servers/wyre-ai-teramind-mcp/ghcr-io-wyre-ai-teramind-mcp-v1-0-0