# OctoWatch DLP (pypi · octowatch-mcp)

Read-only OctoWatch DLP Cloud MCP: risks, idle time, productivity, monitoring.

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- pypi · `octowatch-mcp`: 83/100 (this document), [markdown](https://verifymcp.io/servers/extralabs-octowatch-mcp/octowatch-mcp.md), [page](https://verifymcp.io/servers/extralabs-octowatch-mcp/octowatch-mcp)

## Channel facts

- Registry: `pypi`
- Package: `octowatch-mcp`
- Version: `0.5.1`
- 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**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 1 of 34 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 24 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 4042 tokens (~161/item across 25 items; 22 tools + 3 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 78% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 22 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 24 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the OctoWatch DLP MCP server?

OctoWatch DLP runs locally as a PyPI package, launched with uvx octowatch-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add extralabs-octowatch-mcp -- uvx octowatch-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "extralabs-octowatch-mcp": {
      "command": "uvx",
      "args": [
        "octowatch-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "extralabs-octowatch-mcp": {
      "command": "uvx",
      "args": [
        "octowatch-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add extralabs-octowatch-mcp -- uvx octowatch-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "extralabs-octowatch-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "octowatch-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add extralabs-octowatch-mcp --command uvx --arg octowatch-mcp
```

### Hermes

```yaml
mcp_servers:
  extralabs-octowatch-mcp:
    command: "uvx"
    args: ["octowatch-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "extralabs-octowatch-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "octowatch-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add extralabs-octowatch-mcp -t stdio -c uvx -a octowatch-mcp
```

### Other

```json
{
  "mcpServers": {
    "extralabs-octowatch-mcp": {
      "command": "uvx",
      "args": [
        "octowatch-mcp"
      ]
    }
  }
}
```

## 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 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 82, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-17 (score 66, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-16 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 80, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-14 (score 65, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-13 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (22)

### `octowatch_whoami` (~31 tokens)

Who am I

Show which OctoWatch API host and account the MCP server is using (password never returned).

### `list_users_groups` (~88 tokens)

List users and groups

List users and groups tree (GetUsersGroups2). Type 0=root, 1=group, 2=user.

These Type values are for the UI tree only. For report POST filters use
NodeType 14=group and NodeType 1=user (AliasID).
Cached ~5 min per MCP session; pass refresh=true to force reload.

Input parameters:

- `refresh` (boolean)

### `list_risks` (~258 tokens)

List DLP risks

List or summarize DLP/rule Risks for a period.

Use for: policy/keyword/USB/AI rule hits. Default mode=summary
(by_user from Analytics/Overall; by_rule/by_day/sample from Risks/Overall2).
Not for idle time (get_idle_summary) or timetable deviations (list_anomalies).

Input parameters:

- `compact` (boolean)
- `date_from`: Start datetime YYYY-MM-DD or YYYY-MM-DD HH:MM:SS (full day if date-only).
- `date_to`: End datetime; date-only covers until 23:59:59 that day.
- `fetch_all` (boolean)
- `group_id`: Group filter: TreeviewUsers NodeType=14 (console group id).
- `limit` (integer): Max rows to return (1–500).
- `mode` (string): summary = by_user/by_rule rollup; raw = Risks/Overall2 page.
- `offset` (integer): Pagination offset (0-based).
- `period`: Relative period: today|yesterday|last_7_days|last_30_days (wins over date_from/date_to when set).
- `user_id`: User filter: AliasID as TreeviewUsers NodeType=1.

### `list_anomalies` (~245 tokens)

List formal alerts

List formal Alerts / deviations (POST /api/Alerts/Overall2).

Use for: lateness, overtime, unusual app-share, timetable-fired alerts.
Do NOT use for idle/inactive duration — that is get_idle_summary (InactiveTime).
Do NOT use for DLP keyword/USB policy hits — that is list_risks.

Input parameters:

- `compact` (boolean)
- `date_from`: Start datetime YYYY-MM-DD or YYYY-MM-DD HH:MM:SS (full day if date-only).
- `date_to`: End datetime; date-only covers until 23:59:59 that day.
- `filter_key`: Optional text filter passed to the Cloud API FilterKey.
- `group_id`: Group filter: TreeviewUsers NodeType=14 (console group id).
- `limit` (integer): Max rows to return (1–500).
- `offset` (integer): Pagination offset (0-based).
- `period`: Relative period: today|yesterday|last_7_days|last_30_days (wins over date_from/date_to when set).
- `user_id`: User filter: AliasID as TreeviewUsers NodeType=1.

### `get_idle_summary` (~194 tokens)

Idle time summary

Rank users by inactive (idle) time from Productivity/Overall3.

Use for: 'who was idle longest?', 'idle > N hours', InactiveTime totals.
Do NOT use list_anomalies for idle — Alerts are formal deviations only.

Input parameters:

- `date_from`: Start datetime YYYY-MM-DD or YYYY-MM-DD HH:MM:SS (full day if date-only).
- `date_to`: End datetime; date-only covers until 23:59:59 that day.
- `group_id`: Group filter: TreeviewUsers NodeType=14 (console group id).
- `min_idle_hours`: Only include users with InactiveTime >= this many hours.
- `period`: Relative period: today|yesterday|last_7_days|last_30_days (wins over date_from/date_to when set).
- `user_id`: User filter: AliasID as TreeviewUsers NodeType=1.

### `get_activity_summary` (~165 tokens)

Activity summary

Top apps and sites by ActiveTime (POST /api/Activity/Overall2).

Input parameters:

- `date_from`: Start datetime YYYY-MM-DD or YYYY-MM-DD HH:MM:SS (full day if date-only).
- `date_to`: End datetime; date-only covers until 23:59:59 that day.
- `group_id`: Group filter: TreeviewUsers NodeType=14 (console group id).
- `period`: Relative period: today|yesterday|last_7_days|last_30_days (wins over date_from/date_to when set).
- `raw` (boolean)
- `top_n` (integer): How many top apps/sites to keep.
- `user_id`: User filter: AliasID as TreeviewUsers NodeType=1.

### `get_timesheet` (~149 tokens)

Timesheet

Timesheet / attendance summary (POST /api/TimeSheet/Overall2).

Input parameters:

- `date_from`: Start datetime YYYY-MM-DD or YYYY-MM-DD HH:MM:SS (full day if date-only).
- `date_to`: End datetime; date-only covers until 23:59:59 that day.
- `group_id`: Group filter: TreeviewUsers NodeType=14 (console group id).
- `period`: Relative period: today|yesterday|last_7_days|last_30_days (wins over date_from/date_to when set).
- `raw` (boolean)
- `user_id`: User filter: AliasID as TreeviewUsers NodeType=1.

### `get_productivity_summary` (~148 tokens)

Productivity summary

Per-user productivity rollup (Overall3 + stats + Analytics metrics).

Input parameters:

- `date_from`: Start datetime YYYY-MM-DD or YYYY-MM-DD HH:MM:SS (full day if date-only).
- `date_to`: End datetime; date-only covers until 23:59:59 that day.
- `group_id`: Group filter: TreeviewUsers NodeType=14 (console group id).
- `period`: Relative period: today|yesterday|last_7_days|last_30_days (wins over date_from/date_to when set).
- `raw` (boolean)
- `user_id`: User filter: AliasID as TreeviewUsers NodeType=1.

### `list_reports` (~18 tokens)

List reports

List scheduled report mailing settings and background processing tasks.

### `get_analytics` (~168 tokens)

Get analytics

Analytics rollups: view=overall|disciplina|activity|productivity.

Input parameters:

- `compact` (boolean)
- `date_from`: Start datetime YYYY-MM-DD or YYYY-MM-DD HH:MM:SS (full day if date-only).
- `date_to`: End datetime; date-only covers until 23:59:59 that day.
- `group_id`: Group filter: TreeviewUsers NodeType=14 (console group id).
- `period`: Relative period: today|yesterday|last_7_days|last_30_days (wins over date_from/date_to when set).
- `user_id`: User filter: AliasID as TreeviewUsers NodeType=1.
- `view` (string): Analytics view: overall|disciplina|activity|productivity.

### `get_dashboard` (~174 tokens)

Get dashboard widget

Dashboard widgets (metadata only; screenshot blobs stripped when compact).

Input parameters:

- `compact` (boolean)
- `date_from`: Start datetime YYYY-MM-DD or YYYY-MM-DD HH:MM:SS (full day if date-only).
- `date_to`: End datetime; date-only covers until 23:59:59 that day.
- `group_id`: Group filter: TreeviewUsers NodeType=14 (console group id).
- `num_screens` (integer): Screens tile count.
- `period`: Relative period: today|yesterday|last_7_days|last_30_days (wins over date_from/date_to when set).
- `user_id`: User filter: AliasID as TreeviewUsers NodeType=1.
- `widget` (string): Dashboard widget id (users, risks, applications, …).

### `get_chrono` (~190 tokens)

Chronometry

Chronometry timeline (POST /api/Chrono/Overall2).

Input parameters:

- `compact` (boolean)
- `date_from`: Start datetime YYYY-MM-DD or YYYY-MM-DD HH:MM:SS (full day if date-only).
- `date_to`: End datetime; date-only covers until 23:59:59 that day.
- `filter_key`: Optional text filter passed to the Cloud API FilterKey.
- `group_id`: Group filter: TreeviewUsers NodeType=14 (console group id).
- `limit` (integer): Max rows to return (1–500).
- `offset` (integer): Pagination offset (0-based).
- `period`: Relative period: today|yesterday|last_7_days|last_30_days (wins over date_from/date_to when set).
- `user_id`: User filter: AliasID as TreeviewUsers NodeType=1.

### `get_day_structure` (~217 tokens)

Day structure

Day structure: mode=list (DayStructureList) or detail (GetDayStructure).

detail requires user_id. Filters match console: ProductivityFilter 0–4,
ActivityTypeFilter 0–2 (defaults 0).

Input parameters:

- `activity_type_filter` (integer)
- `compact` (boolean)
- `date_from`: Start datetime YYYY-MM-DD or YYYY-MM-DD HH:MM:SS (full day if date-only).
- `date_to`: End datetime; date-only covers until 23:59:59 that day.
- `group_id`: Group filter: TreeviewUsers NodeType=14 (console group id).
- `mode` (string): list = DayStructureList; detail = GetDayStructure (needs user_id).
- `period`: Relative period: today|yesterday|last_7_days|last_30_days (wins over date_from/date_to when set).
- `productivity_filter` (integer)
- `user_id`: User filter: AliasID as TreeviewUsers NodeType=1.

### `list_monitoring` (~272 tokens)

List monitoring

Single Monitoring list (Sites, Apps, Screens, Keystrokes, Mail, …).

For keyword search across many Monitoring kinds (console Tools → Search),
use search_monitoring(filter_key=…) instead of calling this 13–19 times.

Sensitive kinds return text truncated when compact=true. No binary media.

Input parameters:

- `compact` (boolean)
- `date_from`: Start datetime YYYY-MM-DD or YYYY-MM-DD HH:MM:SS (full day if date-only).
- `date_to`: End datetime; date-only covers until 23:59:59 that day.
- `filter_key`: Optional text filter passed to the Cloud API FilterKey.
- `filter_objects`: Optional FilterObjects JSON/string for Monitoring POST.
- `group_id`: Group filter: TreeviewUsers NodeType=14 (console group id).
- `kind` (string, required): Monitoring table: Sites|Apps|Keystrokes|Mail|…
- `limit` (integer): Max rows to return (1–500).
- `offset` (integer): Pagination offset (0-based).
- `period`: Relative period: today|yesterday|last_7_days|last_30_days (wins over date_from/date_to when set).
- `user_id`: User filter: AliasID as TreeviewUsers NodeType=1.

### `search_monitoring` (~295 tokens)

Search monitoring

Console Tools → Search: parallel Monitoring fan-out with FilterKey.

Use for: 'find keyword X across activity' (sites/apps/keys/mail/files/…).
Prefer this over calling list_monitoring many times.
Not for Risks (list_risks), idle (get_idle_summary), or formal Alerts
(list_anomalies). Does not search SearchQueries.

kinds: optional comma-separated subset (e.g. "Sites,Apps,Mail" or
"sites,mail"). Default = all Tools Search sources.

Input parameters:

- `date_from`: Start datetime YYYY-MM-DD or YYYY-MM-DD HH:MM:SS (full day if date-only).
- `date_to`: End datetime; date-only covers until 23:59:59 that day.
- `filter_key` (string, required): Keyword for Tools → Search fan-out across Monitoring.
- `group_id`: Group filter: TreeviewUsers NodeType=14 (console group id).
- `kinds`: Optional comma-separated kinds, e.g. Sites,Apps,Mail.
- `max_rows` (integer)
- `offset` (integer): Pagination offset (0-based).
- `per_source_limit` (integer)
- `period`: Relative period: today|yesterday|last_7_days|last_30_days (wins over date_from/date_to when set).
- `user_id`: User filter: AliasID as TreeviewUsers NodeType=1.

### `get_activity_detail` (~191 tokens)

Activity detail

Activity drill-down: ActivityWindow (needs activity_name) or CategoryWindow (needs category_guid).

Input parameters:

- `activity_name`
- `category_guid`
- `compact` (boolean)
- `date_from`: Start datetime YYYY-MM-DD or YYYY-MM-DD HH:MM:SS (full day if date-only).
- `date_to`: End datetime; date-only covers until 23:59:59 that day.
- `group_id`: Group filter: TreeviewUsers NodeType=14 (console group id).
- `is_website` (boolean)
- `mode` (string): activity_window needs activity_name; category_window needs category_guid.
- `period`: Relative period: today|yesterday|last_7_days|last_30_days (wins over date_from/date_to when set).
- `user_id`: User filter: AliasID as TreeviewUsers NodeType=1.

### `list_online` (~151 tokens)

List online presence

Online presence (POST /api/Live/Overall2). No webcam or live stream frames.

Input parameters:

- `compact` (boolean)
- `date_from`: Start datetime YYYY-MM-DD or YYYY-MM-DD HH:MM:SS (full day if date-only).
- `date_to`: End datetime; date-only covers until 23:59:59 that day.
- `group_id`: Group filter: TreeviewUsers NodeType=14 (console group id).
- `period`: Relative period: today|yesterday|last_7_days|last_30_days (wins over date_from/date_to when set).
- `user_id`: User filter: AliasID as TreeviewUsers NodeType=1.

### `list_stream_meta` (~189 tokens)

Stream metadata

Desktop video metadata (SPA GET contracts; no DownloadVideo).

which_content: needs user_id; uses DateTo (or period end) as DateTime.
videos: needs user_id + DateFrom/DateTo (UserID header).
downloads: Bearer only (exported file list).

Input parameters:

- `compact` (boolean)
- `date_from`: Start datetime YYYY-MM-DD or YYYY-MM-DD HH:MM:SS (full day if date-only).
- `date_to`: End datetime; date-only covers until 23:59:59 that day.
- `period`: Relative period: today|yesterday|last_7_days|last_30_days (wins over date_from/date_to when set).
- `source` (string): which_content/videos need user_id; downloads is export list.
- `user_id`: User filter: AliasID as TreeviewUsers NodeType=1.

### `list_directory` (~58 tokens)

List directory

Directory reads: users/groups tree, users, groups, computers, additional operators.

users_groups is session-cached (~5 min); pass refresh=true to force reload.

Input parameters:

- `refresh` (boolean)
- `source` (string): Directory Get source.

### `get_user_info` (~186 tokens)

Get user info

User/computer detail reads (SPA GET headers).

user_data / tooltip / group: need user_id (AliasID).
group = group *path* for that user (not load-by-GroupID).
computer / users_from_computer: need computer_guid (ComputerGuid).

Input parameters:

- `compact` (boolean)
- `computer_guid`
- `date_from`: Start datetime YYYY-MM-DD or YYYY-MM-DD HH:MM:SS (full day if date-only).
- `date_to`: End datetime; date-only covers until 23:59:59 that day.
- `period`: Relative period: today|yesterday|last_7_days|last_30_days (wins over date_from/date_to when set).
- `source` (string): User/computer detail source.
- `user_id`: User filter: AliasID as TreeviewUsers NodeType=1.

### `get_account_readonly` (~152 tokens)

Account read-only

Read-only account/profile/license Gets (SPA header contracts).

profiles: GetProfiles2 — ProfilesType 0|1|2; optional user_id + alias_type
(1=user, 14=group); defaults AliasID/AliasType=-1.
timetable/rules/profile_settings/computer_settings: require profile_id.
computer_profiles: optional computer_guid (Guid header).

Input parameters:

- `alias_type`
- `compact` (boolean)
- `computer_guid`
- `profile_id`
- `profiles_type`
- `source` (string): Account/profile/license Get source (no Set*/PIN).
- `user_id`: User filter: AliasID as TreeviewUsers NodeType=1.

### `list_api_coverage` (~26 tokens)

API coverage matrix

Static gap matrix: which console APIs are covered vs intentional out-of-scope.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/extralabs-octowatch-mcp/octowatch-mcp#diagnostics

## Score history

- 2026-09-20: 83
- 2026-09-19: 82
- 2026-09-18: 82
- 2026-09-17: 66
- 2026-09-16: 81
- 2026-09-15: 80
- 2026-09-14: 65
- 2026-09-13: 80
- 2026-09-12: 79
- 2026-09-11: 79
- 2026-09-10: 78
- 2026-09-09: 78
- 2026-09-08: 77
- 2026-09-07: 77
- 2026-09-06: 76
- 2026-09-05: 76
- 2026-09-04: 75
- 2026-09-03: 72
- 2026-09-02: 72
- 2026-09-01: 72
- 2026-08-31: 72
- 2026-08-30: 72
- 2026-08-29: 72
- 2026-08-28: 72
- 2026-08-27: 57

## Common questions

### What is the OctoWatch DLP MCP server?

OctoWatch DLP is an MCP server listed in the public MCP registry as io.github.extralabs/octowatch-mcp. Read-only OctoWatch DLP Cloud MCP: risks, idle time, productivity, monitoring. This page covers its PyPI package (octowatch-mcp).

### Is the OctoWatch DLP MCP server safe to use?

OctoWatch DLP scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 OctoWatch DLP MCP server expose?

OctoWatch DLP exposes 22 tools: octowatch_whoami, list_users_groups, list_risks, list_anomalies, get_idle_summary, and 17 more. Their descriptions and schemas cost roughly 3,565 tokens of context every time the server is loaded.

### Is the OctoWatch DLP MCP server still maintained?

OctoWatch DLP 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 OctoWatch DLP MCP server under?

OctoWatch DLP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/octowatch-mcp/
- Socket report: https://socket.dev/pypi/package/octowatch-mcp
- Repository: https://github.com/extralabs/octowatch-mcp-server
- Website: https://octowatchdlp.com/
- Changelog RSS feed: https://verifymcp.io/servers/extralabs-octowatch-mcp/octowatch-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/extralabs-octowatch-mcp/octowatch-mcp.json
- HTML version of this page: https://verifymcp.io/servers/extralabs-octowatch-mcp/octowatch-mcp