Skip to content

Sync by CHNLSYNC

by chnlsync.com · remote · no sign-in to list tools · v0.2.0 · published by com.chnlsync

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

Changes · 3
CompareRegistry entry

3 tools: 3 change things.

Scanned Oct 21, 2026

3 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Findings

Matches of fixed checks, with the text they matched.

3 info

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Changes things 3Claude Code: ask
  • ask_sync_advisorConsult CHNLSYNC's advisor about the user's IT environment.1 finding

    Why it is in this group

    • The name "ask_sync_advisor" says "sync": a word for a change.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...te advisor workspace is created and its credentials are returned. Later calls: pass session..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Ask the Sync advisor
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • check_copper_retirementLook up US copper/POTS retirement program status by carrier and state.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check copper retirement status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • request_broker_callbackAsk a CHNLSYNC human broker to contact the user about their case.2 findings

    Why it is in this group

    • The name "request_broker_callback" says "request": a word for a change.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...ail with CHNLSYNC. Requires the session credentials returned by ask_sync_advisor. The resul..."

      What this check looks for
    • Info

      The input schema at properties.session_token.description mentions "credential".

      Matched text

      inputSchema.properties.session_token.description: "Private workspace credential."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Request a human broker callback
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.2.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__advisor__check_copper_retirement",
      "mcp__advisor__ask_sync_advisor",
      "mcp__advisor__request_broker_callback"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as advisor. Review it before you use it.