Back to Browse

Telivy MCP Server

Developer ToolsModerate5.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

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

About

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

Security Report

5.2
Moderate5.2Moderate Risk

This is a well-structured MCP server for Telivy's security assessment API with proper authentication, input validation, and error handling. The codebase demonstrates good security practices: credentials are managed via environment variables or request-scoped storage (appropriate for gateway deployments), all API calls use proper URL encoding, and HTTP status codes are distinguished for meaningful error reporting. Permissions are appropriately scoped to read-only operations matching the stated purpose. Minor code quality observations around broad exception handling and optional input validation do not materially impact security. Supply chain analysis found 4 known vulnerabilities in dependencies (2 critical, 0 high severity).

7 files analyzed · 8 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

Telivy API key, from Telivy Portal > Account > IntegrationsRequired

Environment variable: TELIVY_API_KEY

Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.Optional

Environment variable: MCP_TRANSPORT

Credential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.Optional

Environment variable: AUTH_MODE

Log verbosity: debug, info, warn, errorOptional

Environment variable: LOG_LEVEL

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-wyre-ai-telivy-mcp": {
      "env": {
        "AUTH_MODE": "your-auth-mode-here",
        "LOG_LEVEL": "your-log-level-here",
        "MCP_TRANSPORT": "your-mcp-transport-here",
        "TELIVY_API_KEY": "your-telivy-api-key-here"
      },
      "args": [
        "-y",
        "@wyre-ai/telivy-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Telivy MCP Server

MCP server for Telivy's security assessment API for MSPs - external (surface) scans, deep-scan risk assessments, device inventory, M365/Google Workspace user exposure, PII summaries, and finding-level detail, for AI assistants and the WYRE Conduit gateway.

Authentication

Telivy authenticates with a single static API key, generated from the Telivy Portal (Account > Integrations). An OAuth2/Auth0 implicit flow also exists, but the API-key path is simpler and is what MSP integrations use, so that's what this connector uses. The key is sent as the x-api-key HTTP header.

Configuration

Env varDescription
TELIVY_API_KEYAPI key issued by Telivy.
MCP_TRANSPORTstdio (default) or http.
AUTH_MODEenv (default, reads the var above) or gateway (credential arrives per-request via the X-Telivy-Api-Key header, injected by the Conduit gateway).
CONDUIT_S2S_SECRETWhen set, the HTTP transport requires a valid X-Gateway-S2S header (Conduit sidecar auth) on every /mcp request.
LOG_LEVELdebug | info (default) | warn | error.

Tools

External scans

  • telivy_list_external_scans - list external (surface) scans, with search/sort/pagination.
  • telivy_get_external_scan - get a single external scan by assessment ID.
  • telivy_list_external_scan_findings - list the findings for an external scan.
  • telivy_get_external_scan_finding - get details for a single external scan finding by slug.
  • telivy_get_breach_data - get breach records surfaced for an external scan's domain(s).

Risk assessments

  • telivy_list_risk_assessments - list deep-scan risk assessments, with search/sort/pagination/status filters.
  • telivy_get_risk_assessment - get a single risk assessment by ID.
  • telivy_list_risk_assessment_devices - list all deep-scan devices for a risk assessment.
  • telivy_get_risk_assessment_device - get a single deep-scan device by ID.
  • telivy_get_risk_assessment_scan_status - get scan completion status across all devices.
  • telivy_list_m365_users - get Microsoft 365 user accounts with login status and MFA info.
  • telivy_list_gws_users - get Google Workspace user accounts with login and 2SV status.
  • telivy_get_pii_summary - get the PII exposure summary across all devices.

Findings, agent versions, and risk progress

  • telivy_get_agent_versions - get the latest deep-scan agent versions (Windows/Mac).
  • telivy_get_finding - get top-level finding details by slug (e.g. TYPO_SQUATTING, PERSONAL_EMAILS).
  • telivy_get_risk_progress - get a progress report (new/resolved/regressed/open findings) comparing two scan timestamp groups.

Scope

This is a v1, read-only MSP fleet/security-visibility surface, matching this wave's convention of scoping connectors to monitoring/visibility and deferring provisioning-style writes. Explicitly out of scope for now:

  • All write endpoints: creating or updating external scans and risk assessments, rescan-all, uninstall-all, rescanning a single device, convert-to-risk-assessment, and updating monitoring settings. These are provisioning/destructive actions, not read-only visibility.
  • The binary report-download endpoints (GET .../external-scans/{id}/report, GET .../risk-assessments/{id}/report) - they return files, not the structured JSON this connector's tools deal in.
  • GET /api/v1/security/risk-assessments/{id}/domain-change-preview - a preview endpoint for an in-flight domain-change write, out of scope alongside the write it previews.

They can be added as a follow-up if there's demand.

Development

npm install
npm run build
npm test
npm run lint   # tsc --noEmit

Docker

docker build -t telivy-mcp .
docker run -p 8080:8080 -e TELIVY_API_KEY=... telivy-mcp

Reviews

No reviews yet

Be the first to review this server!