For a Clash node, look at the egress before the score

Use EgressScope to see a Clash node's public egress and quality score. It does not read your local config, and it does not replace the client's own connectivity probe.

Updated · Egress Observatory

Two ways to check

When the browser is using that node, open the home page for the domestic / overseas egress and the quality score.

If you already know the node's public IP, pass it to the health-check API. Scripts should read score and choose their own threshold.

Don't mix these up

A client health check mostly says whether the node connects. Low latency is not a high quality score, and a reachable URL does not mean split rules are doing what you think.

This site does not log in to Clash and does not read the config file.

Drop it in a group

After the check, use Copy share text. You get a short note plus a /r/ report link. The other person sees that snapshot, not your live traffic.

Related tools and guides