General Tools
chnlsync.com
Provides information about copper retirement programs and connects users with advisors and brokers for IT environment consultations.
ENDPOINT 1
https://mcp.chnlsync.com/mcp
MCP server metadata
- Name
- CHNLSYNC Sync
- Version
- 0.1.0
Sync is CHNLSYNC's IT advisor for business technology decisions (connectivity, UCaaS, contact center, security). A human broker reviews every recommendation; Sync never names suppliers or quotes pricing on its own. Use check_copper_retirement for copper/POTS retirement status, ask_sync_advisor to consult the advisor on the user's behalf, and request_broker_callback (with the user's explicit consent) to hand off to a human broker.
Known tools 3
check_copper_retirementLook up US copper/POTS retirement program status by carrier and state.
Inferred read-onlyrequest_broker_callbackAsk a CHNLSYNC human broker to contact the user about their case.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.chnlsync-sync]
url = "https://mcp.chnlsync.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"chnlsync-sync": {
"type": "http",
"url": "https://mcp.chnlsync.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: chnlsync-sync
Remote MCP URL: https://mcp.chnlsync.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"chnlsync-sync": {
"url": "https://mcp.chnlsync.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"chnlsync-sync": {
"type": "http",
"url": "https://mcp.chnlsync.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "chnlsync-sync",
"transport": "streamable-http",
"url": "https://mcp.chnlsync.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.