Retrieve live DX spot data by connecting to a DX cluster node over telnet
domain: ve7cc.net · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Open a raw TCP connection to a DX cluster host and port, e.g. dxc.ve7cc.net on port 23; note that some DX Spider-based clusters instead listen on port 7300 or 8000, so confirm the specific node's documented port before connecting.
When prompted, send your amateur radio callsign as the login; most public DX cluster nodes require no password.
Issue read commands such as sh/dx/25 to request the most recent spots, or set/filter and sh/filter to manage a personal filter for what the node sends you going forward.
Parse the resulting line-oriented DX spot format (spotter, frequency, spotted callsign, free-text comment, UTC time/date).
Keep the TCP session open to receive an ongoing real-time stream of newly announced spot lines rather than treating this as a one-shot request.
Known gotchas
Command syntax and prompt behavior vary by cluster software (AR-Cluster, DX Spider, CC Cluster) and by node operator, so consult that specific node's help/MOTD text before scripting against it.
Most public nodes carry no formal API contract or uptime guarantee; treat any single node as potentially unavailable and be ready to fail over to an alternate node from a public telnet-cluster list.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?