# Chnlsync Advisor MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.chnlsync%2Fadvisor
Registry id: `mcp-registry/com.chnlsync/advisor`
Status: live (checked 2026-10-26T19:34:38.530Z)

## Verdict

Chnlsync Advisor MCP server answered 99.97% of Glimind's liveness checks over 30 days, better than 39% of MCP servers, with 589 ms median handshake and 3 outages in 90 days. Its agent-readiness grade is A (100/100) across 3 tools, costing an agent about 1,026 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.97% | 39% of MCP servers |
| Median handshake latency | 589 ms | 44% of MCP servers |
| p95 handshake latency | 2716 ms | — |
| Checks in 30 days | 4,874 | — |
| Outages, 90 days | 3 | — |
| Median recovery | 7 min | — |
| Agent-readiness score | 100/100 (A) | 94% of MCP servers |
| Tools | 3 | — |
| Tool-list size for an agent | ~1,026 tokens | 72% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "chnlsync-advisor-mcp-server": {
      "type": "http",
      "url": "https://mcp.chnlsync.com/mcp"
    }
  }
}
```

Claude Code:

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

## Tools (3)

- `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 descr
- `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 sourc
- `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. R

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.