Isimud MCP Server

Package to get commonly used details of the network interface and access points you are using. The isimud mcp server wraps that behind the Model Context Protocol, so an assistant can use it rather than through you.

What it actually does

Requires Python 3.10+ on Linux. Install with uv:

• List loopback / ethernet / wifi interfaces (classified by kernel type, not by name)
• Per interface: type, operational state, MAC, MTU, carrier, IPv4 / IPv6 addresses, traffic counters (bytes / packets / errors / drops), and throughput rate
• ESSID, BSSID, signal (dBm + %), plus the frequency and current bitrate of the associated AP
• The default interface, default gateway (IPv4 / IPv6), and the configured DNS servers
• List nearby access points (SSID, signal, security) via iwd, NetworkManager, or wpa_supplicant over D-Bus, without root
• watch(): a live stream of link / address / route changes (netlink, no root), to react instead of poll

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the isimud mcp server does with a few real requests.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes.

This entry was verified against Isimud's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.