Mmcp.market

Sync by CHNLSYNC MCP server

by chnlsync.com·com.chnlsync/advisor·v0.2.0
No reviews yet

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

C69/100grade C
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
C69/100

full report

Adoption
New

Little public usage data yet

Reviews

Write one

Nobody has reviewed Sync by CHNLSYNC yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Sync by CHNLSYNC tools (3)

write = sends, deletes, buys or posts
  • ask_sync_advisorFree

    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.

  • check_copper_retirementFree

    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_broker_callbackFree

    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.

Public scan report

scanner v0.1.9 · 2026-09-19 · same rubric, same numbers if you re-run it

1 low
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 827ms20/20
  • Tool poisoning3 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenanceno repository listed3/15
  • Maintainer identityverified namespace with website, no repo4/10

Findings (1)

  • lowNo source repository listedmaint.no-repo
Overall 69/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

Install directly

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

Sync by CHNLSYNC: common questions

Is Sync by CHNLSYNC MCP server safe?
With care: it is graded C, so read the findings first (69/100). Read the Sync by CHNLSYNC safety report
How do I install Sync by CHNLSYNC?
It runs remotely at mcp.chnlsync.com. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Sync by CHNLSYNC need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Sync by CHNLSYNC maintained?
The latest release is v0.2.0.
Is Sync by CHNLSYNC up?
100% of our last 6 checks got an answer. We check remote servers about four times a day.

More from chnlsync.com →