Ssid MCP

What ssid-mcp MCP server does

The ssid-mcp MCP server gives an MCP-capable AI agent access to ssid.ai’s router and MAC-address data. It can retrieve manufacturer-cited factory login information for router, gateway, mesh, and access-point models, including the gateway IP, login host, credential details, reset instructions, and source URL.

It also evaluates whether a model uses a universal default password. The result is based on the recorded credential type and includes a compliance verdict for the UK PSTI and EU CRA patterns. This is a documentation-based measurement, not legal advice.

For MAC addresses, the server returns the registered organization, OUI, address classification, confidence, and source. Private or randomized addresses are identified separately rather than being assigned a potentially incorrect vendor.

How it works

The server communicates with ssid.ai through MCP tools. Router defaults can be requested by a known slug or by providing a brand and model. A brand-and-model request performs an exact resolution; if the model is not exact, the response can include up to five candidate slugs from that brand.

The check_router_compliance tool reads the router’s manufacturer-cited credential type. Values distinguish passwords set during setup, unique credentials printed on a label, app-only administration, static universal credentials, and unknown cases. The response includes the source and the reasoning basis.

lookup_mac accepts a MAC address and classifies it as universal, randomized, multicast, or invalid. For randomized addresses, the vendor is null and the response explains why a normal vendor attribution would be unreliable.

Correction requests are queued for verification against an official manufacturer URL. They are not applied automatically.

Setup and configuration

Run the ssid-mcp MCP server from an MCP host with Node.js 18 or newer. A stdio configuration can launch it with npx -y ssid-mcp, so no API key is needed for the three read tools.

The service also provides a Streamable HTTP endpoint at https://ssid.ai/mcp/http. Clients that do not launch a local stdio process can send JSON-RPC 2.0 requests there; initialization negotiates protocol version 2025-06-18.

Set SSID_API_KEY when using submit_correction. The key is part of ssid Pro, listed at $15 per month in the supplied documentation. Without it, the correction tool returns an upgrade path rather than an error code.

Tools and capabilities

• get_router_defaults: Resolve a router by slug or by brand and model, returning cited login and reset information.
• check_router_compliance: Report whether the model has a universal default password and provide related regime results.
• lookup_mac: Map a MAC address to an OUI organization and identify randomized, multicast, or invalid inputs.
• submit_correction: Propose a sourced change to a router’s login IP, username, password, credential type, or reset steps.

The read tools are described as free and require no API key. Router records carry manufacturer source URLs, while the MAC/OUI data is sourced from the IEEE MA-L registry and re-ingested daily.

Limitations and notes

Coverage depends on the tracked router records and the current ssid.ai data. The supplied snapshot lists 424 router, gateway, mesh, and access-point models and 40,126 indexed MAC/OUI vendors, but these values can change; the live compliance data should be queried for current totals.

A null username or password is meaningful when the credential type explains that no factory credential exists. Agents should not fill such fields with common guesses such as admin/admin. For a router’s factory login after a MAC lookup, call get_router_defaults with the model information.

Correction submissions require an official manufacturer source URL and paid API access. Users can still report an incorrect value for free through ssid.ai’s trust page.