Remote MCP · Endpoint

Sync by CHNLSYNC MCP server

No. Sync by CHNLSYNC answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.chnlsync.com/mcp

The last check completed an MCP handshake.

Registry name
com.chnlsync/advisor
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
190 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
FCC copper retirement lookups and a broker-reviewed IT advisor. No supplier names, no prices.
Listing
From the official MCP registry (active).
Recent checks of Sync by CHNLSYNC
CheckedResultHandshake
1 hour agoHandshake completed190 ms
19 hours agoHandshake completed80 ms
2 days agoHandshake completed73 ms
3 days agoHandshake completed82 ms
4 days agoHandshake completed84 ms
5 days agoHandshake completed92 ms
6 days agoHandshake completed78 ms
8 days agoHandshake completed834 ms
10 days agoHandshake completed77 ms
13 days agoHandshake completed111 ms
15 days agoHandshake completed82 ms
17 days agoHandshake completed113 ms
19 days agoHandshake completed86 ms
21 days agoHandshake completed89 ms
23 days agoHandshake completed95 ms
25 days agoHandshake completed105 ms
27 days agoHandshake completed93 ms
28 days agoHandshake completed177 ms
29 days agoHandshake completed526 ms

The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Sync by CHNLSYNC and makes no claim about it beyond what these checks measured.