network-doctor measures your Wi-Fi, how much lag you get while the line is busy, call quality and your 4G/5G signal. Then it reads your router and proposes a fix. Nothing changes until you say yes.
Speed tests say the line is fine. The real culprit is usually lag under load: when anything uploads or downloads, the router queues your voice packets behind it. network-doctor measures exactly that, on the same UDP path a call uses.
The numbers on the right come from the built-in demo network, the same synthetic data used in every recording on this page.
While uploading, 61% of voice packets arrive later than 150 ms, which is too late to play. Bufferbloat grade: F.
One read-only checkup. You get ranked findings, each with evidence and a fix.
Signal, noise, channel and width, plus the neighbouring networks crowding it. It suggests the least busy channel.
Measures latency while idle, while uploading and while downloading, and grades bufferbloat from A+ to F.
Loss, jitter and late packets from a voice-like UDP stream to the STUN servers Meet and others use.
Finds PPPoE/VPN MTU problems that make some sites hang, and slow or failing DNS.
4G/5G RSRP, RSRQ, SINR and band; Wi-Fi config; clients; QoS. Read straight from the router's own API.
It shows a plan, applies it after you approve, saves a backup, then re-measures so you see the before and after.
It reads the cellular signal, Wi-Fi and clients. Every change starts as a plan showing the current and new values. Nothing is sent until you approve it.
Identifies the router with read-only requests. No login.
Logs in with the password from your OS keychain, and logs out after.
Automatic backup, plus a one-line revert.
verified means tested on real hardware. experimental means written from public protocol docs and tested against synthetic answers. Own one? Tell us if it works: that's how a driver becomes verified.
| Family | Covers | Tier |
|---|---|---|
| Huawei HiLink | 5G CPE 5s/Pro, B310-B818, E5577/E5785 MiFi, E3372 | verified |
| ZTE MiFi (goform) | U20, MU5001, MF971 and most ZTE MiFis | verified |
| ZTE ZXHN | H188A, and likely H298A, F670L and ISP-branded gateways | verified |
| Huawei home gateway | HG630 V2, HG633, HG658 | verified |
| TP-Link Archer | AX / C-series web UI | experimental |
| TP-Link LTE | Archer MR200/MR600, TL-MR6400/MR6500 | experimental |
| TP-Link legacy | Older TL-WR / Archer /userRpm/ UI (read-only) | experimental |
| ASUS | ASUSWRT and Asuswrt-Merlin | experimental |
| AVM FRITZ!Box | TR-064 | experimental |
| MikroTik | RouterOS 7 REST, including the LTE monitor | experimental |
| OpenWrt | ubus JSON-RPC (LuCI builds), SQM status | experimental |
Router not listed? netdoc.py capture saves a masked snapshot of its web API, with no secrets, MACs, SSIDs or public IPs. Attach it to an Add my router issue.
Nothing to pip install: it needs only Python 3.9+, which ships with macOS developer tools and every Linux. It runs on your computer, so it measures your real network.
/plugin marketplace add dav-ayman/network-doctor
/plugin install network-doctor@network-doctor
Then describe the problem in plain words: "my calls keep breaking up", "why is my Wi-Fi slow?", "check my 5G router's signal". You get the skill and 16 MCP tools.
network-doctor-<version>.mcpb from the latest release.When Claude needs your router password, it opens a Terminal window where you type it into your OS keychain. The password never goes into the chat.
git clone https://github.com/dav-ayman/network-doctor
cd network-doctor
python3 plugins/network-doctor/skills/network-doctor/scripts/netdoc.py diagnose --demo
--demo runs on a synthetic network. Drop it to measure yours. netdoc.py --help lists every command.
Routers lock the admin account after a few wrong passwords, and a bad setting can cut you off. So the rules are strict.
They live in the macOS Keychain or Linux Secret Service, and every output is masked.
Each stored password is bound to the router's hardware address, so your home password is never offered to the café's 192.168.1.1.
A rejected password is remembered, and netdoc won't try again until you fix it. That's one attempt per run, ever.
Every write shows the current and new values first. It runs only after you approve, with a backup and an undo.
Not for measuring your network. Claude on the web runs code in a cloud sandbox, which can't see your Wi-Fi or router. Use Claude Code or the Claude Desktop extension: both run locally.
For about 45 seconds the full checkup saturates your upload, then your download. That's how it measures lag under load. Use the quick mode, or skip the load test, if someone is on a call.
macOS is first class, and Linux is supported (Wi-Fi details via iw/nmcli). Windows isn't supported yet.
No telemetry. Measurements reach public STUN servers, Cloudflare's speed endpoints (or Apple's networkQuality on macOS) and 1.1.1.1. Router traffic goes only to your router.
Very likely. Run netdoc.py capture and open an "Add my router" issue. The masked capture is enough for someone to write a driver without owning the hardware.