# Syncro (oci · ghcr.io/wyre-ai/syncro-mcp:v1.4.9)

MCP server for Syncro MSP — customers, tickets, assets, invoices, and more.

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

## Components

- oci · `ghcr.io/wyre-ai/syncro-mcp:v1.4.9`: 53/100 (this document), [markdown](https://verifymcp.io/servers/wyre-ai-syncro-mcp/ghcr-io-wyre-ai-syncro-mcp-v1-4-9.md), [page](https://verifymcp.io/servers/wyre-ai-syncro-mcp/ghcr-io-wyre-ai-syncro-mcp-v1-4-9)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-ai/syncro-mcp:v1.4.9`
- 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**: 0/100
  - Malware scan not yet available for this package.
  - 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.
  - Install-script risk not yet assessed.
  - 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.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 22 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1842 tokens (~83/item across 22 items; 21 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 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 21 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 22 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.
  - Supports UI / widget rendering.

**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 Syncro MCP server?

Syncro runs locally as a container image, launched with docker run --rm -i ghcr.io/wyre-ai/syncro-mcp:v1.4.9. 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-syncro-mcp -- docker run --rm -i ghcr.io/wyre-ai/syncro-mcp:v1.4.9
```

### Cursor

```json
{
  "mcpServers": {
    "wyre-ai-syncro-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/syncro-mcp:v1.4.9"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "wyre-ai-syncro-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/syncro-mcp:v1.4.9"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add wyre-ai-syncro-mcp -- docker run --rm -i ghcr.io/wyre-ai/syncro-mcp:v1.4.9
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wyre-ai-syncro-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/syncro-mcp:v1.4.9"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  wyre-ai-syncro-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/wyre-ai/syncro-mcp:v1.4.9"]
```

### Netclaw

```json
{
  "McpServers": {
    "wyre-ai-syncro-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/syncro-mcp:v1.4.9"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "wyre-ai-syncro-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/syncro-mcp:v1.4.9"
      ]
    }
  }
}
```

## 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-19 (score 53, +1)

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

### 2026-09-17 (score 52, +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 51, +1)

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

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

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

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

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

### 2026-09-09 (score 48, +1)

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

### 2026-09-06 (score 47, +5)

- [functional regression] Security disclosure: unverified → fail
- [functional improvement] Stability: unverified → 0.30

### 2026-09-05 (score 42, 0)

- [functional regression] Security disclosure: fail → unverified

## MCP tools (21)

### `syncro_navigate` (~146 tokens)

Discover available Syncro tools by domain. Returns tool names and descriptions for the selected domain. All tools are callable at any time — this is a help/discovery aid, not a prerequisite.

Input parameters:

- `domain` (string, required): The domain to explore: - customers: Customer management - list, get, create, and update customer accounts and information - tickets: Ticket management - list, get, create, and update support tickets…

### `syncro_status` (~16 tokens)

Show credentials status and available domains

### `syncro_customers_list` (~128 tokens)

List customers in Syncro. Can filter by query, email, phone, or include disabled customers.

Input parameters:

- `business_name` (string): Filter by business name
- `email` (string): Filter by email address
- `include_disabled` (boolean): Include disabled customers in results
- `page` (number): Page number for pagination (default: 1)
- `per_page` (number): Results per page (default: 25)
- `phone` (string): Filter by phone number
- `query` (string): Search query (matches business name, contact name, etc.)

### `syncro_customers_get` (~32 tokens)

Get details for a specific customer by their ID

Input parameters:

- `customer_id` (number, required): The customer ID

### `syncro_customers_create` (~142 tokens)

Create a new customer in Syncro

Input parameters:

- `address` (string): Street address
- `address_2` (string): Address line 2
- `business_name` (string): Business/company name
- `city` (string): City
- `email` (string): Email address
- `firstname` (string): Primary contact first name
- `lastname` (string): Primary contact last name
- `mobile` (string): Mobile phone number
- `notes` (string): Notes about the customer
- `phone` (string): Phone number
- `state` (string): State/Province
- `zip` (string): ZIP/Postal code

### `syncro_customers_search` (~59 tokens)

Search for customers using a query string. Matches against business name, contact name, email, and other fields.

Input parameters:

- `limit` (number): Maximum number of results (default: 25)
- `query` (string, required): Search query string

### `syncro_tickets_list` (~172 tokens)

List tickets in Syncro. Can filter by customer, contact, status, user, problem type, or resolved state.

Input parameters:

- `contact_id` (number): Filter tickets by contact ID
- `customer_id` (number): Filter tickets by customer ID
- `page` (number): Page number for pagination (default: 1)
- `per_page` (number): Results per page (default: 25)
- `problem_type` (string): Filter tickets by problem type
- `query` (string): Search query string
- `resolved` (boolean): Filter by resolved status
- `since` (string): Filter tickets created/updated since date (ISO 8601 format)
- `status` (string): Filter tickets by status
- `user_id` (number): Filter tickets by assigned user ID

### `syncro_tickets_get` (~35 tokens)

Get details for a specific ticket by its ID, including comments

Input parameters:

- `ticket_id` (number, required): The ticket ID

### `syncro_tickets_create` (~127 tokens)

Create a new ticket in Syncro

Input parameters:

- `comment_body` (string): Initial comment/description body
- `comment_subject` (string): Initial comment subject
- `contact_id` (number): Contact ID
- `customer_id` (number, required): Customer ID (required)
- `due_date` (string): Due date (ISO 8601 format)
- `problem_type` (string): Problem type category
- `status` (string): Ticket status
- `subject` (string, required): Ticket subject/title (required)
- `user_id` (number): Assigned user/technician ID

### `syncro_tickets_update` (~93 tokens)

Update an existing ticket in Syncro

Input parameters:

- `due_date` (string): New due date (ISO 8601 format)
- `problem_type` (string): New problem type
- `status` (string): New status
- `subject` (string): New ticket subject
- `ticket_id` (number, required): The ticket ID to update (required)
- `user_id` (number): New assigned user ID

### `syncro_tickets_add_comment` (~91 tokens)

Add a comment to an existing ticket

Input parameters:

- `body` (string, required): The comment body text (required)
- `do_not_email` (boolean): Do not send email notification for this comment
- `hidden` (boolean): Make this a hidden/internal comment
- `subject` (string): Comment subject line
- `ticket_id` (number, required): The ticket ID to add the comment to (required)

### `syncro_assets_list` (~122 tokens)

List assets/configuration items in Syncro. Can filter by customer, asset type, or serial number.

Input parameters:

- `asset_serial` (string): Filter by serial number
- `asset_type` (string): Filter by asset type (e.g., Desktop, Laptop, Server, Network Device)
- `customer_id` (number): Filter assets by customer ID
- `page` (number): Page number for pagination (default: 1)
- `per_page` (number): Results per page (default: 25)
- `query` (string): Search query string

### `syncro_assets_get` (~31 tokens)

Get details for a specific asset by its ID

Input parameters:

- `asset_id` (number, required): The asset ID

### `syncro_assets_search` (~87 tokens)

Search for assets using a query string or serial number. Useful for finding devices by name, serial, or other attributes.

Input parameters:

- `asset_serial` (string): Search by exact serial number
- `customer_id` (number): Limit search to a specific customer
- `limit` (number): Maximum number of results (default: 25)
- `query` (string): Search query string

### `syncro_contacts_list` (~80 tokens)

List contacts in Syncro. Can filter by customer ID or search query.

Input parameters:

- `customer_id` (number): Filter contacts by customer ID
- `page` (number): Page number for pagination (default: 1)
- `per_page` (number): Results per page (default: 25)
- `query` (string): Search query string

### `syncro_contacts_get` (~31 tokens)

Get details for a specific contact by their ID

Input parameters:

- `contact_id` (number, required): The contact ID

### `syncro_contacts_create` (~139 tokens)

Create a new contact in Syncro

Input parameters:

- `address1` (string): Street address line 1
- `address2` (string): Street address line 2
- `city` (string): City
- `customer_id` (number, required): Customer ID this contact belongs to (required)
- `email` (string): Email address
- `mobile` (string): Mobile phone number
- `name` (string, required): Contact name (required)
- `notes` (string): Notes about the contact
- `phone` (string): Phone number
- `state` (string): State/Province
- `zip` (string): ZIP/Postal code

### `syncro_invoices_list` (~113 tokens)

List invoices in Syncro. Can filter by customer, status, or date range.

Input parameters:

- `customer_id` (number): Filter invoices by customer ID
- `page` (number): Page number for pagination (default: 1)
- `per_page` (number): Results per page (default: 25)
- `query` (string): Search query string
- `since_date` (string): Filter invoices since this date (ISO 8601 format)
- `status` (string): Filter invoices by status

### `syncro_invoices_get` (~36 tokens)

Get details for a specific invoice by its ID, including line items

Input parameters:

- `invoice_id` (number, required): The invoice ID

### `syncro_invoices_create` (~75 tokens)

Create a new invoice in Syncro

Input parameters:

- `customer_id` (number, required): Customer ID (required)
- `date` (string): Invoice date (ISO 8601 format, defaults to today)
- `due_date` (string): Due date (ISO 8601 format)
- `notes` (string): Invoice notes

### `syncro_invoices_email` (~69 tokens)

Email an invoice to the customer

Input parameters:

- `cc_emails` (string): CC email addresses (comma-separated)
- `invoice_id` (number, required): The invoice ID to email (required)
- `message` (string): Custom email message body
- `subject` (string): Custom email subject

## Diagnostics

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

## Score history

- 2026-09-20: 53
- 2026-09-19: 53
- 2026-09-18: 52
- 2026-09-17: 52
- 2026-09-16: 51
- 2026-09-15: 51
- 2026-09-14: 50
- 2026-09-13: 50
- 2026-09-12: 49
- 2026-09-11: 49
- 2026-09-10: 48
- 2026-09-09: 48
- 2026-09-08: 47
- 2026-09-07: 47
- 2026-09-06: 47
- 2026-09-05: 42
- 2026-09-04: 42
- 2026-09-03: 42
- 2026-09-02: 42
- 2026-09-01: 42
- 2026-08-31: 42
- 2026-08-30: 42
- 2026-08-29: 42
- 2026-08-28: 42

## Common questions

### What is the Syncro MCP server?

Syncro is an MCP server listed in the public MCP registry as io.github.WYRE-AI/syncro-mcp. MCP server for Syncro MSP, customers, tickets, assets, invoices, and more. This page covers its container image (ghcr.io/wyre-ai/syncro-mcp:v1.4.9).

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

Syncro scores 53 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 Syncro MCP server expose?

Syncro exposes 21 tools: syncro_navigate, syncro_status, syncro_customers_list, syncro_customers_get, syncro_customers_create, and 16 more. Their descriptions and schemas cost roughly 1,824 tokens of context every time the server is loaded.

### Is the Syncro MCP server still maintained?

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

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

## Links

- Repository: https://github.com/WYRE-AI/syncro-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-ai-syncro-mcp/ghcr-io-wyre-ai-syncro-mcp-v1-4-9.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-ai-syncro-mcp/ghcr-io-wyre-ai-syncro-mcp-v1-4-9.json
- HTML version of this page: https://verifymcp.io/servers/wyre-ai-syncro-mcp/ghcr-io-wyre-ai-syncro-mcp-v1-4-9