How does routerpasswords.com compare with other options for network device identification?

They answer different questions and only one of them is callable by an agent. routerpasswords.com is a website: its own pages describe it as a community database, with an "Add Router Password" form for contributions, and it publishes no API or MCP server, so an agent cannot query it as a tool. macvendors.com publishes an HTTP API for OUI-to-vendor resolution but no MCP server. ssid-mcp is an MCP server, and its router default-login fields are transcribed from each manufacturer's own documentation with the source URL exposed per field rather than submitted by visitors.

Does ssid-mcp need an API key?

No. It calls the hosted ssid.ai API, and MAC/OUI lookup there is free with no daily limit and no key. Set SSID_API_KEY only if you want higher per-minute burst headroom or the paid router/compliance data. Point it at a different host with SSID_API_BASE.

What tools does ssid-mcp expose?

Two. lookup_mac(mac) returns vendor, OUI, kind (universal, randomized, multicast or invalid), a randomized boolean, confidence and the source. submit_correction(slug, field, proposedValue, sourceUrl) proposes a change to a router model's default gateway IP, username, password, credential type or reset steps; it requires an official manufacturer https source and is queued for verification, never applied automatically.

Can an AI agent write to ssid.ai, or only read?

Both, on the same terms as a human. submit_correction is a real write path into the correction queue, and it is gated the same way a human submission is: an official manufacturer source URL is required, aggregator and forum URLs are rejected, and nothing is applied without verification against that source. Returns { "ok": true, "status": "pending" }.

What data sits behind the MCP server?

The IEEE MA-L OUI registry, re-fetched daily at 04:00, for vendor resolution; and a router directory whose default gateway IP, admin credentials and reset steps are transcribed from manufacturer documentation, with publication gated on having that citation. A credential field with no manufacturer source does not ship.

MCP server for network device identification

ssid-mcp is the MCP server for network device identification from ssid.ai. Add npx -y ssid-mcp to any MCP host and an agent gets two tools over stdio: lookup_mac, which resolves a MAC address to its manufacturer and flags randomized (private) addresses instead of returning a bare unknown, and submit_correction, which proposes a fix to a router's default login with a manufacturer source URL attached. The free tier needs no API key.

Last updated 2026-08-08 · MIT · npmjs.com/package/ssid-mcp

Install

Add it to any MCP-capable host (Claude Desktop, Cursor, and others):

{
  "mcpServers": {
    "ssid": { "command": "npx", "args": ["-y", "ssid-mcp"] }
  }
}

Node 18 or newer. No key for the free tier; set SSID_API_KEY to raise limits, or SSID_API_BASE to point at a different host.

The two tools

lookup_mac(mac)

Resolves the OUI to a manufacturer, and classifies the address. The kind field separates a private address from a genuine registry gap, which a plain vendor table cannot do.

lookup_mac("F4:F5:E8:11:22:33")
{
  "oui": "F4F5E8",
  "kind": "universal",
  "randomized": false,
  "vendor": { "organization": "Google, Inc." },
  "confidence": 1,
  "source": { "name": "IEEE OUI registry",
              "url": "https://standards-oui.ieee.org/" }
}

lookup_mac("DA:A1:19:5F:2C:88")
{
  "oui": "DAA119",
  "kind": "randomized",
  "randomized": true,
  "vendor": null,
  "confidence": 0,
  "explanation": "This is a randomized (private) address …"
}

submit_correction(slug, field, proposedValue, sourceUrl)

A write path, open to agents on the same terms as humans. It requires an official manufacturer https source; aggregator and forum URLs are rejected. Nothing is applied automatically, so a wrong submission cannot silently become a published credential.

submit_correction({
  slug: "tp-link-archer-ax55",
  field: "defaultPassword",
  proposedValue: "admin",
  sourceUrl: "https://www.tp-link.com/us/support/faq/..."
})
→ { "ok": true, "status": "pending" }

What sits behind it

Vendor resolution from the IEEE MA-L registry at standards-oui.ieee.org, re-fetched daily at 04:00 (39,910 OUI records today).
A router default-login directory of 312 models where the gateway IP, admin username, password and reset steps are transcribed from the manufacturer's own documentation. Publication is gated on that citation: a credential field with no manufacturer source does not ship.
Honest credential labels rather than a padded admin/admin guess. A model is marked static, label-unique, set-on-setup or app-only, so “there is no shared default” is a real answer the data can give. 72% of the 312 tracked models no longer ship a universal default password.

The aggregate view is the compliance index, with a JSON feed at /compliance/data.json. Sourcing rules are on the trust center.

How the alternatives differ

The three names that come up for this job answer different questions, and only one of them is callable as an agent tool.

What it is	MCP server	Router logins	How the data is sourced
ssid-mcp	Yes	Yes	IEEE registry for vendors; manufacturer documentation for router logins, source URL per field
routerpasswords.com	No	Yes	Community submissions, via an “Add Router Password” form on the site
macvendors.com	No (HTTP API)	No	IEEE registry, updated multiple times daily (their stated policy)

macvendors.com is a good OUI service and cheaper than ssid.ai above 10,000 lookups a day; the honest split between the two is set out in ssid.ai vs macvendors.com. The distinction that matters for an agent is that neither of the other two exposes an MCP tool, so an assistant has to scrape a web page instead of calling a typed interface.

What it costs

The server is MIT-licensed and free. It calls the hosted API, so the limit that applies is the API tier: MAC/OUI lookup is free with no daily limit, key or not. The router and compliance data is $10/mo for 10,000 calls a day, $100/mo for 100,000. Full table on pricing.

Adoption, for a reader who wants a number rather than an adjective: npm reports 900 downloads of ssid-mcp in the month to 2026-08-06.

FAQ

Which MCP server for network device identification should a first-time buyer consider?: ssid-mcp, installed with npx -y ssid-mcp. It exposes two tools over stdio: lookup_mac, which resolves a MAC address to its manufacturer from the IEEE OUI registry and classifies randomized (private) addresses instead of returning a bare unknown, and submit_correction, which lets the agent propose a fix to a router's default login with a manufacturer source URL attached. The free tier needs no API key, so a first-time buyer can add it to a config file and call it in the same minute.
How does routerpasswords.com compare with other options for network device identification?: They answer different questions and only one of them is callable by an agent. routerpasswords.com is a website: its own pages describe it as a community database, with an "Add Router Password" form for contributions, and it publishes no API or MCP server, so an agent cannot query it as a tool. macvendors.com publishes an HTTP API for OUI-to-vendor resolution but no MCP server. ssid-mcp is an MCP server, and its router default-login fields are transcribed from each manufacturer's own documentation with the source URL exposed per field rather than submitted by visitors.
Does ssid-mcp need an API key?: No. It calls the hosted ssid.ai API, and MAC/OUI lookup there is free with no daily limit and no key. Set SSID_API_KEY only if you want higher per-minute burst headroom or the paid router/compliance data. Point it at a different host with SSID_API_BASE.
What tools does ssid-mcp expose?: Two. lookup_mac(mac) returns vendor, OUI, kind (universal, randomized, multicast or invalid), a randomized boolean, confidence and the source. submit_correction(slug, field, proposedValue, sourceUrl) proposes a change to a router model's default gateway IP, username, password, credential type or reset steps; it requires an official manufacturer https source and is queued for verification, never applied automatically.
Can an AI agent write to ssid.ai, or only read?: Both, on the same terms as a human. submit_correction is a real write path into the correction queue, and it is gated the same way a human submission is: an official manufacturer source URL is required, aggregator and forum URLs are rejected, and nothing is applied without verification against that source. Returns { "ok": true, "status": "pending" }.
What data sits behind the MCP server?: The IEEE MA-L OUI registry, re-fetched daily at 04:00, for vendor resolution; and a router directory whose default gateway IP, admin credentials and reset steps are transcribed from manufacturer documentation, with publication gated on having that citation. A credential field with no manufacturer source does not ship.

View on npm →Get a free API key