Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Telivy

OCI · GHCR.IO/WYRE-AI/TELIVY-MCP:V1.0.0 · SCANNED SEP 21

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

38 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security0
  • Malware scan not yet available for this package.Unverified
  • 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.Unverified
  • Install-script risk not yet assessed.Unverified
  • 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.Unverified
Provenance & Transparency32
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 821 tokens (~51/item across 16 items; 16 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

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

Telivy runs locally as a container image, launched with docker run --rm -i ghcr.io/wyre-ai/telivy-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.

oci · ghcr.io/wyre-ai/telivy-mcp:v1.0.0

# add to Claude Code
claude mcp add wyre-ai-telivy-mcp -- docker run --rm -i ghcr.io/wyre-ai/telivy-mcp:v1.0.0
// .cursor/mcp.json
{
  "mcpServers": {
    "wyre-ai-telivy-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/telivy-mcp:v1.0.0"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "wyre-ai-telivy-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/telivy-mcp:v1.0.0"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add wyre-ai-telivy-mcp -- docker run --rm -i ghcr.io/wyre-ai/telivy-mcp:v1.0.0
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wyre-ai-telivy-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/telivy-mcp:v1.0.0"
      ],
      "enabled": true
    }
  }
}
# ~/.hermes/config.yaml
mcp_servers:
  wyre-ai-telivy-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/wyre-ai/telivy-mcp:v1.0.0"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "wyre-ai-telivy-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/telivy-mcp:v1.0.0"
      ]
    }
  }
}
// mcp.json
{
  "mcpServers": {
    "wyre-ai-telivy-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/telivy-mcp:v1.0.0"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 38

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Analysed oci/ghcr.io/wyre-ai/telivy-mcp:v1.0.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 16 exposed · ~821 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
telivy_get_agent_versions ~27

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

telivy_get_breach_data ~40

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

NameTypeReqDescription
idstringyesAssessment ID.

No output schema declared.

No examples provided.

telivy_get_external_scan ~29

Get a single external scan by assessment ID.

NameTypeReqDescription
idstringyesAssessment ID.

No output schema declared.

No examples provided.

telivy_get_external_scan_finding ~42

Get details for a single external scan finding by slug.

NameTypeReqDescription
idstringyesAssessment ID.
slugstringyesFinding slug.

No output schema declared.

No examples provided.

telivy_get_finding ~41

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

NameTypeReqDescription
slugstringyesFinding slug.

No output schema declared.

No examples provided.

telivy_get_pii_summary ~35

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

NameTypeReqDescription
idstringyesAssessment UUID.

No output schema declared.

No examples provided.

telivy_get_risk_assessment ~30

Get a single risk assessment by ID.

NameTypeReqDescription
idstringyesAssessment UUID.

No output schema declared.

No examples provided.

telivy_get_risk_assessment_device ~48

Get a single deep-scan device by ID.

NameTypeReqDescription
deviceIdstringyesDeep scan target (device) UUID.
idstringyesAssessment UUID.

No output schema declared.

No examples provided.

telivy_get_risk_assessment_scan_status ~36

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

NameTypeReqDescription
idstringyesAssessment UUID.

No output schema declared.

No examples provided.

telivy_get_risk_progress ~85

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

NameTypeReqDescription
compareWithTimestampGroupstringThe scan timestamp group to compare against. Defaults to the previous scan if omitted.
currentTimestampGroupstringyesThe current/most recent scan timestamp group.
idstringyesAssessment UUID.

No output schema declared.

No examples provided.

telivy_list_external_scan_findings ~30

List the findings for an external scan.

NameTypeReqDescription
idstringyesAssessment ID.

No output schema declared.

No examples provided.

telivy_list_external_scans ~123

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

NameTypeReqDescription
agencyIdstringTELIVY_ADMIN-only: scope results to a specific agency (ignored by non-admin API keys).
assessmentSortBystringField to sort by. Defaults to createdAt.
limitnumberMaximum results to return. Defaults to 100.
offsetnumberPagination offset.
searchstringFree-text search query.
sortOrderstringSort order. Defaults to DESC.

No output schema declared.

No examples provided.

telivy_list_gws_users ~38

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

NameTypeReqDescription
idstringyesAssessment UUID.

No output schema declared.

No examples provided.

telivy_list_m365_users ~38

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

NameTypeReqDescription
idstringyesAssessment UUID.

No output schema declared.

No examples provided.

telivy_list_risk_assessment_devices ~34

List all deep-scan devices for a risk assessment.

NameTypeReqDescription
idstringyesAssessment UUID.

No output schema declared.

No examples provided.

telivy_list_risk_assessments ~145

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

NameTypeReqDescription
agencyIdstringTELIVY_ADMIN-only: scope results to a specific agency (ignored by non-admin API keys).
assessmentSortBystringField to sort by. Defaults to createdAt.
limitnumberMaximum results to return. Defaults to 100.
offsetnumberPagination offset.
scanStatusarrayFilter to one or more scan statuses.
searchstringFree-text search query.
sortOrderstringSort order. Defaults to DESC.

No output schema declared.

No examples provided.

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:v1.0.0).

Is the Telivy MCP server safe to use?

Telivy scores 38 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 21 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 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.