Sync by CHNLSYNC is a remote MCP server that gives an AI agent 3 tools, among them ask_sync_advisor, check_copper_retirement, request_broker_callback. It answers at https://mcp.chnlsync.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 11 of 11 times since 3 September 2026; the last check, on 19 October 2026, succeeded.
FCC copper retirement lookups and a broker-reviewed IT advisor. No supplier names, no prices.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
ask_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 Inputs: message, session_id, session_token, company_name, pain |
check_copper_retirement | 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"; ``st Inputs: carrier, state |
request_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 ``boo Inputs: session_id, session_token, contact_name, contact_email |
Every block below points at https://mcp.chnlsync.com/mcp. Pick your client and copy.
claude mcp add --transport http sync-by-chnlsync https://mcp.chnlsync.com/mcp
{
"mcpServers": {
"sync-by-chnlsync": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.chnlsync.com/mcp"]
}
}
}{
"mcpServers": {
"sync-by-chnlsync": {
"url": "https://mcp.chnlsync.com/mcp"
}
}
}{
"servers": {
"sync-by-chnlsync": {
"type": "http",
"url": "https://mcp.chnlsync.com/mcp"
}
}
}{
"context_servers": {
"sync-by-chnlsync": {
"url": "https://mcp.chnlsync.com/mcp"
}
}
}{
"mcpServers": {
"sync-by-chnlsync": {
"serverUrl": "https://mcp.chnlsync.com/mcp"
}
}
}{
"mcpServers": {
"sync-by-chnlsync": {
"url": "https://mcp.chnlsync.com/mcp"
}
}
}name: Sync by CHNLSYNC
version: 0.0.1
schema: v1
mcpServers:
- name: Sync by CHNLSYNC
type: streamable-http
url: https://mcp.chnlsync.com/mcp{
"mcpServers": {
"sync-by-chnlsync": {
"httpUrl": "https://mcp.chnlsync.com/mcp"
}
}
}{
"mcpServers": {
"sync-by-chnlsync": {
"type": "http",
"url": "https://mcp.chnlsync.com/mcp"
}
}
}{
"mcpServers": {
"sync-by-chnlsync": {
"url": "https://mcp.chnlsync.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.chnlsync.com%2Fmcp&type=streamable_http&id=sync-by-chnlsync&name=Sync%20by%20CHNLSYNC
It answered our last check on 19 October 2026 in 429 ms. Over 11 checks since 3 September 2026 it answered 11. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by chnlsync.com and served from mcp.chnlsync.com, the vendor's own domain: https://mcp.chnlsync.com/mcp.
3, as returned by the server's own tools/list on 2 September 2026: ask_sync_advisor, check_copper_retirement, request_broker_callback.
It answered our last check on 19 October 2026 in 429 ms. Over 11 checks since 3 September 2026 it answered 11.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.chnlsync.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.chnlsync. Endpoint host: mcp.chnlsync.com. ARD identifier: urn:air:com.chnlsync:mcp:advisor.
First indexed 2 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.