Sync by CHNLSYNC
by chnlsync.com in Other
FCC copper retirement lookups and a broker-reviewed IT advisor. No supplier names, no prices.
https://mcp.chnlsync.com/mcp- Tools
- 3
- open to any client
- Uptime
- 100%
- last 30 days
- Response time
- 433 ms
- 494 ms slowest 5%
- Last check
- Passed
- 3 h ago, next in 3 h
Reliability
Status and outage history · Atom feed · Watch with other listings
How to connect
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"sync-by-chnlsync": {
"type": "http",
"url": "https://mcp.chnlsync.com/mcp"
}
}
}3 tools
- 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 source_url). ``carrier`` accepts display names like "AT&T", "Lumen", "Frontier"; ``state`` is a two-letter abbreviation…
- 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 description of what is not working) — a private advisor workspace is created and its credentials are returned. Later calls…
- 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. Requires the session credentials returned by ask_sync_advisor. The result's ``book_url`` is an optional scheduling link…
Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 3 h ago | Passed | 200 | 408 ms |
| 13 h ago | Passed | 200 | 433 ms |
| 22 h ago | Passed | 200 | 470 ms |
| 32 h ago | Passed | 200 | 400 ms |
| 41 h ago | Passed | 200 | 454 ms |
Show 10 older checks
| 2 days ago | Passed | 200 | 418 ms |
| 2 days ago | Passed | 200 | 448 ms |
| 3 days ago | Passed | 200 | 456 ms |
| 3 days ago | Passed | 200 | 379 ms |
| 4 days ago | Passed | 200 | 427 ms |
| 4 days ago | Passed | 200 | 387 ms |
| 5 days ago | Passed | 200 | 447 ms |
| 5 days ago | Passed | 200 | 432 ms |
| 5 days ago | Passed | 200 | 443 ms |
| 6 days ago | Passed | 200 | 505 ms |