Log inSubmit server
RadioChron logo

RadioChron

Local-first Wi-Fi and BLE diagnosis, radio history, connectivity checks, and change recording over MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install RadioChron

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "radiochron": {
      "command": "npx",
      "args": [
        "-y",
        "radiochron-mcp"
      ],
      "env": {
        "RADIOCHRON_CHRONICLE_PATH": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y radiochron-mcp

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 6d ago.

Overview

RadioChron MCP server collects native Wi-Fi and Bluetooth Low Energy evidence, then returns structured findings for assistants and operator workflows. Its tools cover WLAN state, nearby networks, signal analysis, sampling, connectivity stages, BLE observation, and a local rotating chronicle. Use it when an agent needs to investigate wireless incidents without interpreting raw operating-system output itself. The server runs over stdio and can also be installed as a Rust binary or launched through the npm package.

Use cases

  • Diagnose a Wi-Fi incident across radio, authentication, DHCP, DNS, and Internet stages
  • Inspect nearby BSS signal, security, channel width, and load information
  • Sample RSSI, link rate, and roaming behavior over a period
  • Track BLE advertisements and evaluate expected-device disappearance
  • Record and review local wireless changes over time

Key features

  • Structured Wi-Fi status and BSS analysis
  • Staged connectivity diagnosis
  • Cancelable Wi-Fi sampling with progress
  • Native BLE scanning without GATT connections
  • Local rotating JSONL chronicle
  • Composite incident diagnosis

Tools17

What RadioChron lets your agent do. Expand a tool for its parameters.

Self-reported~328 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

4/4 checks healthy over the last 34d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · radiochron-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads205Package downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed17Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How RadioChron works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about RadioChron

RadioChron is an MCP server that connects AI clients to local Wi-Fi and Bluetooth Low Energy radio data. Its main tools diagnose incidents, inspect WLAN interfaces and nearby networks, test staged connectivity, scan and analyze BLE advertisements, and record recent wireless changes in a local chronicle.

Install it with `npx -y radiochron-mcp`, or install the Rust binary from the repository with Cargo. The npm package includes verified native binaries for supported Windows, Linux, and macOS targets. A compiled binary can be registered with any stdio MCP client using its executable command.

Set `RADIOCHRON_CHRONICLE_PATH` to override the local chronicle directory. If it is unset, RadioChron uses `%LOCALAPPDATA%\\RadioChron` on Windows, `~/Library/Application Support/RadioChron` on macOS, or the XDG state directory on Linux.

Yes. Call `diagnose_incident` for a combined response covering WLAN state, RF analysis, connection stages, available Windows WLAN history, recent chronicle entries, and optional BLE evidence. It keeps each collector's result or actionable error separate.

Yes. `ble_scan` listens for advertisements during the requested scan window and does not perform GATT connections. It uses WinRT on Windows, BlueZ on Linux, and CoreBluetooth on macOS, subject to the host platform's Bluetooth permissions and adapter availability.

Related MCP servers

All in Monitoring All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewRadioChron AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/radiochron?style=directory)](https://allmcps.com/mcp/radiochron)
HTML Embed
<a href="https://allmcps.com/mcp/radiochron"><img src="https://allmcps.com/api/badge/radiochron?style=directory" alt="RadioChron on AllMCPs" /></a>