Sync by CHNLSYNC MCP server
com.chnlsync/advisorchnlsync.comstreamable-httpv0.2.0Scanned
FCC copper retirement lookups and a broker-reviewed IT advisor. No supplier names, no prices.
3 tools: 3 change things.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Sync by CHNLSYNC MCP server can do
The Sync by CHNLSYNC MCP server is published by chnlsync.com, a domain the MCP Registry verified. It has 3 tools. It can create or change data (3 tools: check_copper_retirement, ask_sync_advisor and request_broker_callback), but cannot delete data. None of its tools only reads.
1 tool brings in text other people can write (request_broker_callback).
The fixed checks matched 3 findings (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 12, 2026, version 0.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
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".
What this check looks forMatched text
description: "...te advisor workspace is created and its credentials are returned. Later calls: pass session..."
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.Reads text others write2 findings
Why it is in this group
- The name "request_broker_callback" says "request": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...ail with CHNLSYNC. Requires the session credentials returned by ask_sync_advisor. The resul..."
- Info
The input schema at properties.session_token.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.session_token.description: "Private workspace credential."
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.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:35 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.chnlsync.com/mcp: tools/list returned 3 tools to an anonymous client, including check_copper_retirement (write), ask_sync_advisor (write), request_broker_callback (write)
Findings
Matches of fixed checks, with the text they matched.
- Infoask_sync_advisor
The description mentions "credentials".
What this check looks forMatched text
description: "...te advisor workspace is created and its credentials are returned. Later calls: pass session..."
The description mentions "credentials".
What this check looks forMatched text
description: "...ail with CHNLSYNC. Requires the session credentials returned by ask_sync_advisor. The resul..."
The input schema at properties.session_token.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.session_token.description: "Private workspace credential."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
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/mcpclaude mcp add --transport http advisor https://mcp.chnlsync.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as advisor. Review it before you use it.
Capability tags behind 1 rule
- mcp__advisor__request_broker_callback untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.chnlsync/advisor/verify?hash=af7bb75c5274a51aa62abfb9780084f5a61b31c390fc0f8af20ac3b3322d1b45" | jq -e '.changed == false'Pinned hash af7bb75c5274, from Nov 12, 2026, 21:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.chnlsync/advisor/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.chnlsync/advisor)Source: MCP Registry. Synced Oct 21, 2026, 17:52 UTC.
Sync by CHNLSYNC MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Sync by CHNLSYNC MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 3 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Sync by CHNLSYNC MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Sync by CHNLSYNC MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Sync by CHNLSYNC MCP server have?
- 3 tools: 3 write. check_copper_retirement, ask_sync_advisor and request_broker_callback.
Does the Sync by CHNLSYNC MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Sync by CHNLSYNC MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Sync by CHNLSYNC MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.