MCP.Market

Telivy MCP server

by WYRE-AI·io.github.WYRE-AI/telivy-mcp·v1.0.1

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

B70/100grade B
What users say
No reviews yet
Be the first
Safety scan
B70/100

not scanned yet

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Telivy yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Telivy tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Telivy compares

Against every graded Security MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
70/100
higher than 33% of 915 Security servers

Release history: 2 versions in the registry since 2026-09-20, latest 2026-10-17, typically one every 27 days.

Install Telivy in Claude Code, Cursor or VS Code

claude mcp add telivy-mcp -- docker run -i --rm ghcr.io/wyre-ai/telivy-mcp:v1.0.1
Add to Cursor

What the publisher says

From the Telivy repository's README, as published. We do not edit it. Read it on GitHub

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

Tools

External scans

  • telivylistexternal_scans - list external (surface) scans, with search/sort/pagination.
  • telivygetexternal_scan - get a single external scan by assessment ID.
  • telivylistexternalscanfindings - list the findings for an external scan.
  • telivygetexternalscanfinding - get details for a single external scan finding by slug.
  • telivygetbreach_data - get breach records surfaced for an external scan's domain(s).

Risk assessments

  • telivylistrisk_assessments - list deep-scan risk assessments, with search/sort/pagination/status filters.
  • telivygetrisk_assessment - get a single risk assessment by ID.
  • telivylistriskassessmentdevices - list all deep-scan devices for a risk assessment.
  • telivygetriskassessmentdevice - get a single deep-scan device by ID.
  • telivygetriskassessmentscan_status - get scan completion status across all devices.
  • telivylistm365_users - get Microsoft 365 user accounts with login status and MFA info.
  • telivylistgws_users - get Google Workspace user accounts with login and 2SV status.
  • telivygetpii_summary - get the PII exposure summary across all devices.

Findings, agent versions, and risk progress

  • telivygetagent_versions - get the latest deep-scan agent versions (Windows/Mac).
  • telivygetfinding - get top-level finding details by slug (e.g. TYPOSQUATTING, PERSONALEMAILS).
  • telivygetrisk_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

Nothing above is checked by us. What we check is on the safety report.

Telivy: common questions

Is Telivy MCP server safe?
Mostly: it is graded B (70/100). Read the Telivy safety report
How do I install Telivy?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Telivy need an API key?
Yes. The registry entry asks for TELIVY_API_KEY.
Is Telivy maintained?
The last commit was 23 days ago (2026-10-13). The latest release is v1.0.1.
What can I use instead of Telivy?
Servers from other publishers that do the same job: Skylos MCP server, Snyk MCP server and CrowdStrike Falcon MCP Server.

Alternatives to Telivy

Same job from other publishers: the closest match first, then the best rated.

  • Skylos
    Dead code, security, secrets detection and code quality for Python, TypeScript, Go.
    C
  • Snyk
    Easily find and fix security issues in your applications leveraging Snyk platform capabilities.
    B
  • CrowdStrike Falcon MCP Server
    Connects AI agents with CrowdStrike Falcon for security analysis and automation.
    A
  • Wireshark
    Professional network analysis with tshark. Security audits, deep-dives, and threat detection.
    A
  • Virustotal
    MCP server for querying VirusTotal API with comprehensive security analysis tools.
    B

More from WYRE-AI →