# Sync by CHNLSYNC (remote · mcp.chnlsync.com)

FCC copper retirement lookups and a broker-reviewed IT advisor. No supplier names, no prices.

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

## Components

- remote · `mcp.chnlsync.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/com-chnlsync-advisor/mcp.md), [page](https://verifymcp.io/servers/com-chnlsync-advisor/mcp)

## Channel facts

- Endpoint: `https://mcp.chnlsync.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-25.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 641 tokens (~213/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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.

## Install

### How do I install the Sync by CHNLSYNC MCP server?

Sync by CHNLSYNC is a hosted endpoint at https://mcp.chnlsync.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-chnlsync-advisor 'https://mcp.chnlsync.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-chnlsync-advisor": {
      "url": "https://mcp.chnlsync.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-chnlsync-advisor": {
      "type": "http",
      "url": "https://mcp.chnlsync.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-chnlsync-advisor]
url = "https://mcp.chnlsync.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-chnlsync-advisor": {
      "type": "remote",
      "url": "https://mcp.chnlsync.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-chnlsync-advisor --url 'https://mcp.chnlsync.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-chnlsync-advisor:
    url: "https://mcp.chnlsync.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-chnlsync-advisor": {
      "Transport": "http",
      "Url": "https://mcp.chnlsync.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-chnlsync-advisor -t streamable-http -u 'https://mcp.chnlsync.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-chnlsync-advisor": {
      "type": "http",
      "url": "https://mcp.chnlsync.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-25 (score 77, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 77, +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-22 (score 76, +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-20 (score 75, +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-18 (score 74, +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-16 (score 73, +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-13 (score 72, +1)

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

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

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

## MCP tools (3)

### `check_copper_retirement` (~118 tokens)

Check copper retirement status

Look up US copper/POTS retirement program status by carrier and state.

Deterministic read of CHNLSYNC's FCC-sourced dataset (CC BY 4.0 — cite
the returned source_url). ``carrier`` accepts display names like "AT&T",
"Lumen", "Frontier"; ``state`` is a two-letter abbreviation. Omit both
for the full dataset.

Input parameters:

- `carrier`: Carrier display name, e.g. AT&T.
- `state`: Two-letter US state, e.g. TX.

Output parameters:

- `as_of`: As-of date of static records, not of latest_filings.
- `latest_filings` (array): Up to 20 reviewed matching filings.
- `license` (string): Reuse license; attribution is required.
- `records` (array): Carrier/state entries matching the filters.
- `source` (string): Source methodology and limitations.
- `source_url` (string): Attribution URL for the published dataset.

### `ask_sync_advisor` (~242 tokens)

Ask the Sync advisor

Consult CHNLSYNC's advisor about the user's IT environment.

First call: omit session_id/session_token and provide company_name plus
pain (a plain-language description of what is not working) — a private
advisor workspace is created and its credentials are returned. Later
calls: pass session_id, session_token AND conversation_id back to continue
the same conversation. Persist all three privately across turns. Incomplete
continuation handles are rejected before any write; recover the previous
tool result instead of creating another workspace. Never automatically retry
a failed write: it may already have been recorded.
Replies never contain supplier names or pricing — those come only after
a human broker review, via the claim_url or a requested callback.

Input parameters:

- `company_name`: Company name; required for a new workspace.
- `conversation_id`: Returned conversation ID; required for follow-up turns.
- `message` (string, required): The user's technology question; no secrets.
- `pain`: What is not working; required for a new workspace.
- `session_id`: Returned workspace ID; required for continuation.
- `session_token`: Returned private token; required with session_id.

Output parameters:

- `assistant_message` (string): Buyer-safe advisor response.
- `claim_url` (string): Private claim link; share only with the workspace owner.
- `conversation_id` (string): Pass back with both session credentials next turn.
- `disclosure` (string): Human review precedes supplier and pricing disclosure.
- `environment_summary`: Initial workspace summary.
- `follow_up_questions` (array): Questions that clarify the user's needs.
- `missing_info`: Initial information gaps.
- `review_status`: Current human-review status, when available.
- `session_id` (string): Workspace handle to retain with conversation_id.
- `session_token` (string): Private credential; retain, never publish.

### `request_broker_callback` (~188 tokens)

Request a human broker callback

Ask a CHNLSYNC human broker to contact the user about their case.

Only call this with the user's explicit consent to share their name and
email with CHNLSYNC. Requires the session credentials returned by
ask_sync_advisor. The result's ``book_url`` is an optional scheduling
link you may offer the user as a next step ("pick a time now"); the
callback is already queued and a broker will reach out either way, so
never present booking as required or as a confirmed appointment. Do not
automatically retry after a timeout: the request may already be recorded.

Input parameters:

- `contact_email` (string, required): Email the user explicitly consented to share.
- `contact_name` (string, required): Name the user consented to share.
- `session_id` (string, required): Workspace ID returned by the advisor.
- `session_token` (string, required): Private workspace credential.

Output parameters:

- `book_url`: Optional scheduling link; booking is not required.
- `disclosure` (string): Human-review disclosure supplied by the backend.
- `status` (string): Callback request recorded, not yet completed.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-chnlsync-advisor/mcp#diagnostics

## Score history

- 2026-09-25: 77
- 2026-09-24: 77
- 2026-09-23: 76
- 2026-09-22: 76
- 2026-09-21: 75
- 2026-09-20: 75
- 2026-09-19: 74
- 2026-09-18: 74
- 2026-09-17: 73
- 2026-09-16: 73
- 2026-09-15: 72
- 2026-09-14: 72
- 2026-09-13: 72
- 2026-09-12: 71
- 2026-09-11: 71
- 2026-09-10: 70
- 2026-09-09: 70
- 2026-09-08: 59
- 2026-09-07: 59
- 2026-09-06: 58
- 2026-09-05: 58
- 2026-09-04: 57
- 2026-09-03: 57
- 2026-09-02: 57

## Common questions

### What is the Sync by CHNLSYNC MCP server?

Sync by CHNLSYNC is an MCP server listed in the public MCP registry as com.chnlsync/advisor. FCC copper retirement lookups and a broker-reviewed IT advisor. No supplier names, no prices. This page covers its hosted endpoint (https://mcp.chnlsync.com/mcp).

### Is the Sync by CHNLSYNC MCP server safe to use?

Sync by CHNLSYNC scores 77 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 Sync by CHNLSYNC MCP server expose?

Sync by CHNLSYNC exposes 3 tools: check_copper_retirement, ask_sync_advisor, request_broker_callback. Their descriptions and schemas cost roughly 548 tokens of context every time the server is loaded.

### Does the Sync by CHNLSYNC MCP server require authentication?

No. We connected to Sync by CHNLSYNC without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Sync by CHNLSYNC MCP server still maintained?

Sync by CHNLSYNC is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.chnlsync.com/mcp
- Website: https://chnlsync.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-chnlsync-advisor/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-chnlsync-advisor/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-chnlsync-advisor/mcp