# Telivy (oci · ghcr.io/wyre-ai/telivy-mcp)

MCP server for Telivy's security assessment API for MSPs.

- Trust score: 39/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- oci · `ghcr.io/wyre-ai/telivy-mcp`: 39/100 (this document), [markdown](https://verifymcp.io/servers/wyre-ai-telivy-mcp/ghcr-io-wyre-ai-telivy-mcp.md), [page](https://verifymcp.io/servers/wyre-ai-telivy-mcp/ghcr-io-wyre-ai-telivy-mcp)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-ai/telivy-mcp`
- Version: `v1.0.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-10-18.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **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**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 821 tokens (~51/item across 16 items; 16 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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: 1 category.** A category scored 0 because we could not verify it: 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 Telivy MCP server?

Telivy runs locally as a container image, launched with docker run --rm -i -e TELIVY_API_KEY -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/telivy-mcp:v1.0.1. 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-telivy-mcp -- docker run --rm -i -e TELIVY_API_KEY -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/telivy-mcp:v1.0.1
```

This image reads TELIVY_API_KEY, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Cursor

```json
{
  "mcpServers": {
    "wyre-ai-telivy-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "TELIVY_API_KEY",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/telivy-mcp:v1.0.1"
      ]
    }
  }
}
```

This image reads TELIVY_API_KEY, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### VS Code

```json
{
  "servers": {
    "wyre-ai-telivy-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "TELIVY_API_KEY",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/telivy-mcp:v1.0.1"
      ]
    }
  }
}
```

This image reads TELIVY_API_KEY, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Codex

```bash
codex mcp add wyre-ai-telivy-mcp -- docker run --rm -i -e TELIVY_API_KEY -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/telivy-mcp:v1.0.1
```

This image reads TELIVY_API_KEY, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wyre-ai-telivy-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "TELIVY_API_KEY",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/telivy-mcp:v1.0.1"
      ],
      "enabled": true
    }
  }
}
```

This image reads TELIVY_API_KEY, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Hermes

```yaml
mcp_servers:
  wyre-ai-telivy-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "TELIVY_API_KEY", "-e", "MCP_TRANSPORT", "-e", "AUTH_MODE", "-e", "LOG_LEVEL", "ghcr.io/wyre-ai/telivy-mcp:v1.0.1"]
```

This image reads TELIVY_API_KEY, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Netclaw

```json
{
  "McpServers": {
    "wyre-ai-telivy-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "TELIVY_API_KEY",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/telivy-mcp:v1.0.1"
      ]
    }
  }
}
```

This image reads TELIVY_API_KEY, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Other

```json
{
  "mcpServers": {
    "wyre-ai-telivy-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "TELIVY_API_KEY",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/telivy-mcp:v1.0.1"
      ]
    }
  }
}
```

This image reads TELIVY_API_KEY, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

## 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-10-18 (score 39, +1)

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

### 2026-10-17 (score 38)

First indexed and scored.

## MCP tools (16)

### `telivy_list_external_scans` (~123 tokens)

List external (surface) scans - lightweight, agentless domain/email security assessments.

Input parameters:

- `agencyId` (string): TELIVY_ADMIN-only: scope results to a specific agency (ignored by non-admin API keys).
- `assessmentSortBy` (string): Field to sort by. Defaults to createdAt.
- `limit` (number): Maximum results to return. Defaults to 100.
- `offset` (number): Pagination offset.
- `search` (string): Free-text search query.
- `sortOrder` (string): Sort order. Defaults to DESC.

### `telivy_get_external_scan` (~29 tokens)

Get a single external scan by assessment ID.

Input parameters:

- `id` (string, required): Assessment ID.

### `telivy_list_external_scan_findings` (~30 tokens)

List the findings for an external scan.

Input parameters:

- `id` (string, required): Assessment ID.

### `telivy_get_external_scan_finding` (~42 tokens)

Get details for a single external scan finding by slug.

Input parameters:

- `id` (string, required): Assessment ID.
- `slug` (string, required): Finding slug.

### `telivy_get_breach_data` (~40 tokens)

Get breach records surfaced for an external scan's domain(s) (dark-web/credential exposure).

Input parameters:

- `id` (string, required): Assessment ID.

### `telivy_list_risk_assessments` (~145 tokens)

List risk assessments - deep-scan (agent-based) fleet security assessments, optionally filtered by scan status.

Input parameters:

- `agencyId` (string): TELIVY_ADMIN-only: scope results to a specific agency (ignored by non-admin API keys).
- `assessmentSortBy` (string): Field to sort by. Defaults to createdAt.
- `limit` (number): Maximum results to return. Defaults to 100.
- `offset` (number): Pagination offset.
- `scanStatus` (array): Filter to one or more scan statuses.
- `search` (string): Free-text search query.
- `sortOrder` (string): Sort order. Defaults to DESC.

### `telivy_get_risk_assessment` (~30 tokens)

Get a single risk assessment by ID.

Input parameters:

- `id` (string, required): Assessment UUID.

### `telivy_list_risk_assessment_devices` (~34 tokens)

List all deep-scan devices for a risk assessment.

Input parameters:

- `id` (string, required): Assessment UUID.

### `telivy_get_risk_assessment_device` (~48 tokens)

Get a single deep-scan device by ID.

Input parameters:

- `deviceId` (string, required): Deep scan target (device) UUID.
- `id` (string, required): Assessment UUID.

### `telivy_get_risk_assessment_scan_status` (~36 tokens)

Get scan completion status across all devices in a risk assessment.

Input parameters:

- `id` (string, required): Assessment UUID.

### `telivy_list_m365_users` (~38 tokens)

Get Microsoft 365 user accounts with login status and MFA info for a risk assessment.

Input parameters:

- `id` (string, required): Assessment UUID.

### `telivy_list_gws_users` (~38 tokens)

Get Google Workspace user accounts with login and 2SV status for a risk assessment.

Input parameters:

- `id` (string, required): Assessment UUID.

### `telivy_get_pii_summary` (~35 tokens)

Get the PII exposure summary across all devices in a risk assessment.

Input parameters:

- `id` (string, required): Assessment UUID.

### `telivy_get_agent_versions` (~27 tokens)

Get the latest Telivy deep-scan agent versions available (Windows and Mac).

### `telivy_get_finding` (~41 tokens)

Get top-level finding details by slug (e.g. TYPO_SQUATTING, PERSONAL_EMAILS).

Input parameters:

- `slug` (string, required): Finding slug.

### `telivy_get_risk_progress` (~85 tokens)

Get a risk progress report comparing two scan timestamp groups for an assessment (new/resolved/regressed/open findings).

Input parameters:

- `compareWithTimestampGroup` (string): The scan timestamp group to compare against. Defaults to the previous scan if omitted.
- `currentTimestampGroup` (string, required): The current/most recent scan timestamp group.
- `id` (string, required): Assessment UUID.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/wyre-ai-telivy-mcp/ghcr-io-wyre-ai-telivy-mcp#diagnostics

## Score history

- 2026-10-18: 39
- 2026-10-17: 38

## Common questions

### What is the Telivy MCP server?

Telivy is an MCP server listed in the public MCP registry as io.github.WYRE-AI/telivy-mcp. MCP server for Telivy's security assessment API for MSPs. This page covers its container image (ghcr.io/wyre-ai/telivy-mcp).

### Is the Telivy MCP server safe to use?

Telivy 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 Telivy MCP server expose?

Telivy exposes 16 tools: telivy_list_external_scans, telivy_get_external_scan, telivy_list_external_scan_findings, telivy_get_external_scan_finding, telivy_get_breach_data, and 11 more. Their descriptions and schemas cost roughly 821 tokens of context every time the server is loaded.

### Is the Telivy MCP server still maintained?

Telivy is still listed as active in the MCP registry. We last reached this channel on 18 October 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 Telivy MCP server under?

Telivy 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

- GitHub Container Registry: https://ghcr.io/wyre-ai/telivy-mcp
- Repository: https://github.com/WYRE-AI/telivy-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-ai-telivy-mcp/ghcr-io-wyre-ai-telivy-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-ai-telivy-mcp/ghcr-io-wyre-ai-telivy-mcp.json
- HTML version of this page: https://verifymcp.io/servers/wyre-ai-telivy-mcp/ghcr-io-wyre-ai-telivy-mcp