Sync by CHNLSYNC MCP Server

by chnlsync Your server? Claim it

answering

Sync by CHNLSYNC is answering right now. Last checked 4 min ago. It exposes 3 tools.

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

Uptime history 68 days of history · worst day 92%

68 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

442 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 7

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 September 2026. No other catalogue keeps this.

12 Oct a tool changed version

9 Sep 3 tools changed the parameters they ask for ask_sync_advisor, check_copper_retirement, request_broker_callback

9 Sep 2 tool descriptions were rewritten ask_sync_advisor, request_broker_callback

9 Sep a tool changed version

Nothing serious here today

Today is the operative word: we check Sync by CHNLSYNC every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://mcp.chnlsync.com/mcp

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

ask

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 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.

copper

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"; ``state`` is a two-letter abbreviation. Omit both for the full dataset.

request

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 ``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.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.chnlsync.com/mcp	streamable-http	answering	427 ms	4 min ago

Alternatives to Sync by CHNLSYNC

same job, measured the same way

Office Suite

by theluckystrike

Local office proxy for invoices, spreadsheets and supplier statement open-item checks.

local only

Bootstrapware RFQ

by bootstrapware

Configure buyer and supplier request-for-quote apps. No titles, quotes, prices, or file bytes.

answering

Supplier Invoice Duplicates

by theluckystrike

Review duplicate supplier invoice candidates with grouped local evidence; no payment approval.

local only

Fruityvice MCP

by mrfentmen

Fruit nutrition data: calories, sugar, fat and carbs per fruit, with lookup by name and nutrient

120 installs/wk local only

Pharmasync

by ayeongo

Read-only NHS medicine supply data: shortages, SSPs, price concessions and dm+d lookups.

local only

pit.world MCP server

by pit

MCP server for private web search (no API key) and Moshpit name lookups. No logs, no cookies.

97 installs/wk local only

GoMain

by gomain

Domain availability and prices from 40+ registrars, name checks, DNS setup, and a domain broker

15 tools answering

Supplier Directory

by theluckystrike

A supplier directory that does not rot: contacts, payment terms, lead times, due-review report.

10 tools local only

Sync by CHNLSYNC — questions

Answers built from our own checks of this server.

What can Sync by CHNLSYNC do?

It exposes 3 tools, read directly from the server on our last check. Among them: ask_sync_advisor, check_copper_retirement, request_broker_callback. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Sync by CHNLSYNC working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 442 ms. The bar chart above shows every period we have measured.

How do I connect Sync by CHNLSYNC?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Sync by CHNLSYNC need an API key?

No. Sync by CHNLSYNC completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Sync by CHNLSYNC?

It answers our handshake in 442 ms on average, which is faster than 28% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.