WiFi Scanner MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Use scan_wifi_networks to list nearby Wi-Fi networks, get_current_wifi for the active connection, and analyze_wifi_channels for congestion and router channel advice. All tools are read-only and local.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_wifi_networksA | Scan for Wi-Fi networks near this computer and list them with name (SSID), signal strength (dBm, %, quality and 1-4 bars), channel, band (2.4/5/6 GHz), security type (open/WEP/WPA/WPA2/WPA3/enterprise) and whether this computer is connected to it. Use it when the user asks which Wi-Fi networks are around, which one is strongest, or to find a specific network. Read-only; does not connect to anything. |
| get_current_wifiA | Show the Wi-Fi network this computer is connected to right now: name, BSSID, signal, channel, band, security and link speed when available. Read-only. |
| analyze_wifi_channelsA | Analyze nearby access points per band and channel, score interference, recommend the least crowded channel for a router on 2.4 GHz (1/6/11) and 5 GHz, rate congestion on the channel this computer uses, and flag insecure nearby networks (open, WEP, old WPA). Use it for "why is my Wi-Fi slow", "which channel should my router use" or a Wi-Fi site survey. Read-only. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct concern: current connection, nearby network listing, and channel/congestion analysis. The only potential confusion is that analyze_wifi_channels also scans nearby APs, overlapping with scan_wifi_networks, but its descriptions clarify it is for interference scoring and recommendations rather than enumeration.
All three names follow a consistent snake_case verb_wifi_noun pattern (scan_wifi_networks, get_current_wifi, analyze_wifi_channels) with clear, predictable verbs. No style mixing or vague verbs.
Three tools is on the thin side but each earns its place in a narrowly scoped read-only diagnostic server. Nothing feels redundant or missing at the tool-count level.
The read-only survey/lifecycle is well covered: enumerate networks, inspect the current link, and analyze channels for congestion and security. Minor gaps exist around exporting/persisting survey results or adapter-level diagnostics, but agents can work around these.