Sync by CHNLSYNC
REMOTE · MCP.CHNLSYNC.COM · SCANNED SEP 25
FCC copper retirement lookups and a broker-reviewed IT advisor. No supplier names, no prices.
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
remote · mcp.chnlsync.com
claude mcp add --transport http com-chnlsync-advisor 'https://mcp.chnlsync.com/mcp'
{
"mcpServers": {
"com-chnlsync-advisor": {
"url": "https://mcp.chnlsync.com/mcp"
}
}
} {
"servers": {
"com-chnlsync-advisor": {
"type": "http",
"url": "https://mcp.chnlsync.com/mcp"
}
}
} [mcp_servers.com-chnlsync-advisor] url = "https://mcp.chnlsync.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-chnlsync-advisor": {
"type": "remote",
"url": "https://mcp.chnlsync.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-chnlsync-advisor --url 'https://mcp.chnlsync.com/mcp' --transport streamable-http
mcp_servers:
com-chnlsync-advisor:
url: "https://mcp.chnlsync.com/mcp" {
"McpServers": {
"com-chnlsync-advisor": {
"Transport": "http",
"Url": "https://mcp.chnlsync.com/mcp"
}
}
} assistant mcp add com-chnlsync-advisor -t streamable-http -u 'https://mcp.chnlsync.com/mcp'
{
"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.
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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +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.
- 22 Sept 26 +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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +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.
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 25 Sept 2026 · Probed https://mcp.chnlsync.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=chnlsync.com | CN=YE2,O=Let's Encrypt,C=US | 26 Aug 2026 | 24 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 66e83b6e4a012626059f528630ac02ad856 |
| SANs: *.chnlsync.com, chnlsync.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.chnlsync.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| chnlsync.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.chnlsync.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.chnlsync.com/mcp | Inconclusive | 406 |
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 →
ask_sync_advisor Ask the Sync advisor ~242
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company_name | – | – | Company name; required for a new workspace. |
| conversation_id | – | – | Returned conversation ID; required for follow-up turns. |
| message | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| assistant_message | string | yes | Buyer-safe advisor response. |
| claim_url | string | yes | Private claim link; share only with the workspace owner. |
| conversation_id | string | yes | Pass back with both session credentials next turn. |
| disclosure | string | yes | Human review precedes supplier and pricing disclosure. |
| environment_summary | – | – | Initial workspace summary. |
| follow_up_questions | array | yes | Questions that clarify the user's needs. |
| missing_info | – | – | Initial information gaps. |
| review_status | – | yes | Current human-review status, when available. |
| session_id | string | yes | Workspace handle to retain with conversation_id. |
| session_token | string | yes | Private credential; retain, never publish. |
No examples provided.
check_copper_retirement Check copper retirement status ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| carrier | – | – | Carrier display name, e.g. AT&T. |
| state | – | – | Two-letter US state, e.g. TX. |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | yes | As-of date of static records, not of latest_filings. |
| latest_filings | array | yes | Up to 20 reviewed matching filings. |
| license | string | yes | Reuse license; attribution is required. |
| records | array | yes | Carrier/state entries matching the filters. |
| source | string | yes | Source methodology and limitations. |
| source_url | string | yes | Attribution URL for the published dataset. |
No examples provided.
request_broker_callback Request a human broker callback ~188
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_email | string | yes | Email the user explicitly consented to share. |
| contact_name | string | yes | Name the user consented to share. |
| session_id | string | yes | Workspace ID returned by the advisor. |
| session_token | string | yes | Private workspace credential. |
| Name | Type | Req | Description |
|---|---|---|---|
| book_url | – | yes | Optional scheduling link; booking is not required. |
| disclosure | string | yes | Human-review disclosure supplied by the backend. |
| status | string | yes | Callback request recorded, not yet completed. |
No examples provided.
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.