mercury-mesh-watcher

Detect Mercury peer changes in Tailscale meshes via port 9443 probes.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/TitoPrausee/nexus-toti --skill mercury-mesh-watcher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mercury-mesh-watcher
Source: https://github.com/TitoPrausee/nexus-toti/tree/main/data/skills/devops/mercury-mesh-watcher
Command: npx skills add https://github.com/TitoPrausee/nexus-toti --skill mercury-mesh-watcher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the need to manually inspect a Tailscale mesh for Mercury-enabled peers, letting you track new, missing, and changed nodes without wasting LLM turns or operator time.

Core Features & Use Cases

  • Change Detection: Compares each scan against saved peer history to identify new Mercury peers and offline peers.
  • Mesh Scanning: Parses Tailscale status output and probes candidate hosts on port 9443 to verify Mercury service availability.
  • Operational Alerts: Sends direct Telegram notifications only when meaningful mesh changes occur and maintains a lightweight JSON status file for dashboards or follow-up tools.

Quick Start

Ask the agent to run the Mercury Mesh Watcher once, compare the current Tailscale peers with saved state, and report any new or offline Mercury nodes.

Frequently Asked Questions about mercury-mesh-watcher

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor Tailscale peers for offline nodes and new connections?

You can monitor Tailscale peers by parsing Tailscale CLI status output and comparing it against a persistent JSON state file. This detects new or offline Mercury-enabled nodes and sends Telegram alerts only when mesh changes occur.

How does change detection work for a Tailscale mesh network?

Mesh change detection works by probing candidate Tailscale hosts on port 9443 to verify Mercury service availability. It compares each scan against saved peer history to identify new Mercury peers and offline peers, replacing manual checks.

Can I send Telegram alerts when a Tailscale node goes offline?

Yes, you can send direct Telegram Bot API alerts when a Tailscale node goes offline. The automated state comparison triggers notifications only when meaningful mesh changes occur, avoiding alert fatigue.

Do I need cron to automate Tailscale mesh monitoring?

Yes, cron is required for long-running infrastructure monitoring and automated peer discovery. Scheduling the state comparison via cron ensures continuous offline detection and notification workflows without manual intervention.

What is the best way to track Mercury service availability in a Tailscale mesh?

The best way to track Mercury service availability is probing candidate hosts on port 9443 and maintaining a lightweight JSON status file. This automated approach replaces repeated manual peer checks and enables dashboard integration.

Why does my Tailscale mesh monitoring require persistent JSON state?

Persistent JSON state is required to compare current scan results against saved peer history. Without this state file, the monitoring process cannot detect new or offline Mercury nodes or determine when to trigger Telegram alerts.