Syncro
OCI · GHCR.IO/WYRE-TECHNOLOGY/SYNCRO-MCP:V1.4.7
MCP server for Syncro MSP — customers, tickets, assets, invoices, and more.
Available components
Last scanned (3 hours ago)
Scores higher than 82% of OCI servers
Category CRM and Sales
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
- 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.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 57 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1842 tokens (~83/item across 22 items; 21 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 22 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
- Supports UI / widget rendering.Pass
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.
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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 −3
No change was recorded against any check on this day. Stability & Change Management went from 97 to 80.
- 10 Oct 26 +3
No change was recorded against any check on this day. Stability & Change Management went from 80 to 97. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Oct 26 −3
- Stability: pass → 0.80 functional
- 4 Oct 26 0
- Stability: 0.97 → pass security
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 17 Oct 2026 · Analysed oci/ghcr.io/wyre-technology/syncro-mcp:v1.4.7
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 →
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 →
syncro_assets_get ~31
Get details for a specific asset by its ID
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | number | yes | The asset ID |
No output schema declared.
No examples provided.
syncro_assets_list ~122
List assets/configuration items in Syncro. Can filter by customer, asset type, or serial number.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
syncro_assets_search ~87
Search for assets using a query string or serial number. Useful for finding devices by name, serial, or other attributes.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
syncro_contacts_create ~139
Create a new contact in Syncro
| Name | Type | Req | Description |
|---|---|---|---|
| address1 | string | – | Street address line 1 |
| address2 | string | – | Street address line 2 |
| city | string | – | City |
| customer_id | number | yes | Customer ID this contact belongs to (required) |
| string | – | Email address | |
| mobile | string | – | Mobile phone number |
| name | string | yes | Contact name (required) |
| notes | string | – | Notes about the contact |
| phone | string | – | Phone number |
| state | string | – | State/Province |
| zip | string | – | ZIP/Postal code |
No output schema declared.
No examples provided.
syncro_contacts_get ~31
Get details for a specific contact by their ID
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | number | yes | The contact ID |
No output schema declared.
No examples provided.
syncro_contacts_list ~80
List contacts in Syncro. Can filter by customer ID or search query.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
syncro_customers_create ~142
Create a new customer in Syncro
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Street address |
| address_2 | string | – | Address line 2 |
| business_name | string | – | Business/company name |
| city | string | – | City |
| 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 |
No output schema declared.
No examples provided.
syncro_customers_get ~32
Get details for a specific customer by their ID
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | number | yes | The customer ID |
No output schema declared.
No examples provided.
syncro_customers_list ~128
List customers in Syncro. Can filter by query, email, phone, or include disabled customers.
| Name | Type | Req | Description |
|---|---|---|---|
| business_name | string | – | Filter by business name |
| 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.) |
No output schema declared.
No examples provided.
syncro_customers_search ~59
Search for customers using a query string. Matches against business name, contact name, email, and other fields.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of results (default: 25) |
| query | string | yes | Search query string |
No output schema declared.
No examples provided.
syncro_invoices_create ~75
Create a new invoice in Syncro
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | number | yes | 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 |
No output schema declared.
No examples provided.
syncro_invoices_email ~69
Email an invoice to the customer
| Name | Type | Req | Description |
|---|---|---|---|
| cc_emails | string | – | CC email addresses (comma-separated) |
| invoice_id | number | yes | The invoice ID to email (required) |
| message | string | – | Custom email message body |
| subject | string | – | Custom email subject |
No output schema declared.
No examples provided.
syncro_invoices_get ~36
Get details for a specific invoice by its ID, including line items
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | number | yes | The invoice ID |
No output schema declared.
No examples provided.
syncro_invoices_list ~113
List invoices in Syncro. Can filter by customer, status, or date range.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
syncro_navigate ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | 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… |
No output schema declared.
No examples provided.
syncro_status ~16
Show credentials status and available domains
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
syncro_tickets_add_comment ~91
Add a comment to an existing ticket
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | 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 | yes | The ticket ID to add the comment to (required) |
No output schema declared.
No examples provided.
syncro_tickets_create ~127
Create a new ticket in Syncro
| Name | Type | Req | Description |
|---|---|---|---|
| comment_body | string | – | Initial comment/description body |
| comment_subject | string | – | Initial comment subject |
| contact_id | number | – | Contact ID |
| customer_id | number | yes | Customer ID (required) |
| due_date | string | – | Due date (ISO 8601 format) |
| problem_type | string | – | Problem type category |
| status | string | – | Ticket status |
| subject | string | yes | Ticket subject/title (required) |
| user_id | number | – | Assigned user/technician ID |
No output schema declared.
No examples provided.
syncro_tickets_get ~35
Get details for a specific ticket by its ID, including comments
| Name | Type | Req | Description |
|---|---|---|---|
| ticket_id | number | yes | The ticket ID |
No output schema declared.
No examples provided.
syncro_tickets_list ~172
List tickets in Syncro. Can filter by customer, contact, status, user, problem type, or resolved state.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
syncro_tickets_update ~93
Update an existing ticket in Syncro
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The ticket ID to update (required) |
| user_id | number | – | New assigned user ID |
No output schema declared.
No examples provided.
How do I install the Syncro MCP server?
Syncro runs locally as a container image, launched with docker run --rm -i -e SYNCRO_SUBDOMAIN -e SYNCRO_API_KEY -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-technology/syncro-mcp:v1.4.7. 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-technology/syncro-mcp:v1.4.7
claude mcp add wyre-technology-syncro-mcp -- docker run --rm -i -e SYNCRO_SUBDOMAIN -e SYNCRO_API_KEY -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-technology/syncro-mcp:v1.4.7
This image reads SYNCRO_SUBDOMAIN, SYNCRO_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.
What is the Syncro MCP server?
Syncro is an MCP server listed in the public MCP registry as io.github.wyre-technology/syncro-mcp. MCP server for Syncro MSP, customers, tickets, assets, invoices, and more. This page covers its container image (ghcr.io/wyre-technology/syncro-mcp:v1.4.7).
Is the Syncro MCP server safe to use?
Syncro scores 51 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 17 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 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.