# RadioChron [Health: Active]

**Category:** 📊 Monitoring  
**Repository:** https://github.com/sergii-ziborov/radiochron-mcp  
**GitHub Stars:** 1  
**npm Downloads (last month):** 205  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/radiochron

## Description
Local-first Wi-Fi status, BSS analysis, history, connectivity diagnosis, and chronicle.

## Tools
Capabilities this server exposes over MCP:

- **diagnose_incident** — Orchestrate Wi-Fi, connectivity, history, chronicle, and optional native BLE evidence in one compact response
- **wifi_status** — Current state of every WLAN interface
- **wifi_networks** — Nearby BSS records with real dBm, security, width, and load; summary or full detail
- **wifi_analyze** — Signal, contention, roaming, security, and scan-quality findings
- **wifi_sample** — Cancelable RSSI/rate/roaming sampling with progress
- **wifi_scan** — Native Wi-Fi refresh with per-interface completion/failure
- **connectivity_diagnose** — Separate radio, authentication, IP assignment, gateway, DNS, TCP, portal, TLS, quality, and Internet stages
- **chronicle_start** — Start the local rotating change-only JSONL recorder
- **chronicle_stop** — Stop and flush the recorder
- **chronicle_status** — Recorder state, path, counters, and latest error
- **chronicle_recent** — Recent entries from active and rotated files
- **ble_scan** — Scan native adapters without connecting, normalize advertisements, update histories, and return risk evidence
- **ble_identify** — Identify a caller-supplied advertisement and hash its payload
- **ble_tracker_reset** — Clear process-local BLE history and apply detector policy
- **ble_observe** — Add an externally collected timed observation
- **ble_histories** — First/last seen, recurrence, sensors, movement sessions, and RSSI summaries
- **ble_evaluate** — Time-based disappearance findings for expected identities

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "radiochron": {
    "command": "npx",
    "args": ["-y","radiochron-mcp"],
    "env": {
      "RADIOCHRON_CHRONICLE_PATH": ""
    }
  }
}
```

**Requires environment variables:** `RADIOCHRON_CHRONICLE_PATH` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What RadioChron MCP server does

The RadioChron MCP server gives an MCP client access to local wireless diagnostics. It combines native radio collection with the shared RadioChron Rust core and returns typed results, findings, errors, and execution status rather than exposing only unstructured operating-system output.

Its main focus is Wi-Fi incident investigation. The tools can report the state of every WLAN interface, refresh and inspect nearby BSS records, analyze signal and contention, sample RSSI and roaming over time, and separate connectivity stages such as authentication, IP assignment, gateway access, DNS, TCP, TLS, captive portals, quality, and Internet reachability.

Bluetooth Low Energy support is observation-oriented. The server can scan adapters without making GATT connections, identify caller-provided advertisements, retain process-local histories, accept externally collected observations, and evaluate disappearance evidence for expected identities. A combined incident operation can include optional BLE evidence alongside Wi-Fi, connectivity, Windows WLAN history when available, and chronicle entries.

## How it works

The RadioChron MCP server exposes typed tools through MCP over standard input and output. With no command-line arguments, the installed binary serves MCP when its input is a pipe. The `radiochron mcp` command makes that mode explicit. A terminal connected directly to standard input is treated as an interactive invocation and receives help instead.

`diagnose_incident` is the main starting point for a composite investigation. It coordinates the available collectors and asks the shared classifier for one incident assessment. Individual sections report success, returned data, or an actionable error, so an unavailable collector does not remove the other evidence. Caller-supplied targets are required before network targets are contacted.

Long-running work has cancellation or progress behavior where supported. The Wi-Fi sampler reports progress and can be cancelled. BLE scans use the native platform APIs: WinRT on Windows, BlueZ on Linux, and CoreBluetooth on macOS. The scan listens for advertisements during the requested window and does not connect to devices.

## Setup and configuration

Install the verified native npm package with `npx -y radiochron-mcp`, or build and install the Rust binary from the repository with Cargo. Prebuilt npm users do not need a Rust toolchain. Building on Debian or Ubuntu requires `libdbus-1-dev` and `pkg-config` for the BlueZ adapter.

A stdio client can register the installed executable with a command such as `radiochron`. The optional `RADIOCHRON_CHRONICLE_PATH` environment variable changes where the local chronicle is stored. Without it, the default is platform-specific: `%LOCALAPPDATA%\\RadioChron` on Windows, `~/Library/Application Support/RadioChron` on macOS, or the XDG state directory on Linux.

On macOS 11 and later, the terminal or host application launching the process needs Bluetooth permission for BLE scanning. Linux BLE collection depends on the BlueZ adapter. The available Windows WLAN history tool is platform-specific and is backed by WLAN AutoConfig.

## Tools and capabilities

- Inspect interface association and current WLAN state with `wifi_status`.
- Refresh nearby networks with `wifi_scan`, then retrieve BSS signal, security, width, and load data with `wifi_networks`.
- Analyze signal quality, contention, roaming, security, and scan quality with `wifi_analyze`.
- Run staged connection checks with `connectivity_diagnose`.
- Record change-only JSONL events with `chronicle_start`, `chronicle_stop`, `chronicle_status`, and `chronicle_recent`.
- Collect, identify, reset, summarize, and evaluate BLE observations with the `ble_*` tools.
- Produce a compact cross-source incident response with `diagnose_incident`.

## Limitations and notes

The RadioChron MCP server is a pure-Rust MCP server and command-line application. The related Node package does not provide MCP, and the unattended collector and desktop application are separate projects. BLE identities based only on generic private addresses can remain ephemeral; iBeacon and Eddystone UID data may provide stronger identity. The server records local chronicle data, but the material does not describe remote storage or a hosted service.

_Full upstream README: https://allmcps.com/mcp/radiochron/readme_