# ai.ssid/ssid-mcp (remote · ssid.ai)

Manufacturer-cited router default logins and compliance check, plus MAC/OUI vendor lookup. Free.

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-22

## Components

- remote · `ssid.ai`: 66/100 (this document), [markdown](https://verifymcp.io/servers/ai-ssid-ssid-mcp/ssid.md), [page](https://verifymcp.io/servers/ai-ssid-ssid-mcp/ssid)
- npm · `ssid-mcp`: 82/100, [markdown](https://verifymcp.io/servers/ai-ssid-ssid-mcp/ssid-mcp.md), [page](https://verifymcp.io/servers/ai-ssid-ssid-mcp/ssid-mcp)

## Channel facts

- Endpoint: `https://ssid.ai/mcp/http`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-22.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 665 tokens (~166/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the ai.ssid/ssid-mcp server?

ai.ssid/ssid-mcp is a hosted endpoint at https://ssid.ai/mcp/http, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ai-ssid-ssid-mcp 'https://ssid.ai/mcp/http'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-ssid-ssid-mcp": {
      "url": "https://ssid.ai/mcp/http"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-ssid-ssid-mcp": {
      "type": "http",
      "url": "https://ssid.ai/mcp/http"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-ssid-ssid-mcp]
url = "https://ssid.ai/mcp/http"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-ssid-ssid-mcp": {
      "type": "remote",
      "url": "https://ssid.ai/mcp/http",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-ssid-ssid-mcp --url 'https://ssid.ai/mcp/http' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-ssid-ssid-mcp:
    url: "https://ssid.ai/mcp/http"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-ssid-ssid-mcp": {
      "Transport": "http",
      "Url": "https://ssid.ai/mcp/http"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-ssid-ssid-mcp -t streamable-http -u 'https://ssid.ai/mcp/http'
```

### Other

```json
{
  "mcpServers": {
    "ai-ssid-ssid-mcp": {
      "type": "http",
      "url": "https://ssid.ai/mcp/http"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 64, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-16 (score 64)

First indexed and scored.

## MCP tools (4)

### `get_router_defaults` (~180 tokens)

Router factory login (manufacturer-cited)

Default gateway IP, admin username and password (or the fact that there is none), credential type and factory-reset steps for a router or gateway model, each cited to the manufacturer's own documentation with the source URL. Pass the ssid.ai slug, or brand plus model. Use after lookup_mac identifies the vendor, or whenever a user asks for a router's default login, factory password, gateway address or reset procedure. Covers the 409-model ssid.ai directory; no listing or wildcard search.

Input parameters:

- `brand` (string): Manufacturer, e.g. TP-Link, Netgear, ASUS
- `model` (string): Model as printed on the device, e.g. Archer AX55
- `slug` (string): ssid.ai router slug, e.g. tp-link-archer-ax55 (from ssid.ai/routers/<slug>)

### `check_router_compliance` (~99 tokens)

Universal default password check (UK PSTI / EU CRA pattern)

Whether a router model still ships a universal default password, the pattern prohibited for consumer connectable products under the UK PSTI Act and targeted by the EU Cyber Resilience Act, based on the manufacturer-cited credential type, with the ssid.ai Router Compliance Index totals for context. Pass the ssid.ai slug (get it from get_router_defaults). Documentation reading, not legal advice.

Input parameters:

- `slug` (string, required): ssid.ai router slug

### `lookup_mac` (~187 tokens)

MAC / OUI vendor lookup

Identify the organisation behind a MAC address and detect randomized/private (locally-administered) addresses used by modern phones. Resolves the IEEE registries longest-prefix-first, so an address inside a block the IEEE subdivided returns the company that actually holds it (MA-M, MA-S or IAB) rather than the MA-L registrar. Returns vendor, blockType (MA-L | MA-M | MA-S | IAB), block start/end for a sub-block, OUI, kind, randomized flag, confidence and the source registry file. A randomized address keeps vendor: null and adds cidRegistrant when its prefix is a registered Company ID (DA:A1:19 is Google's). For the router's factory login, call get_router_defaults next.

Input parameters:

- `mac` (string, required): A MAC address in any format, e.g. F4:F5:E8:11:22:33

### `submit_correction` (~142 tokens)

Propose a router default-login correction

Propose a fix to a router model's default gateway IP, username, password, credential type, or reset steps on ssid.ai. Requires an official manufacturer source URL (never an aggregator/forum). Queued for verification — never applied automatically. Use the router's slug from ssid.ai/routers/<slug>.

Input parameters:

- `field` (string, required): Which field is wrong
- `proposedValue` (string, required): The correct value, per the cited source
- `slug` (string, required): The router's ssid.ai slug, e.g. 'tp-link-archer-ax55'
- `sourceUrl` (string, required): Official https manufacturer source confirming the correct value

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-ssid-ssid-mcp/ssid#diagnostics

## Score history

- 2026-09-22: 66
- 2026-09-21: 66
- 2026-09-20: 65
- 2026-09-19: 65
- 2026-09-18: 65
- 2026-09-17: 64
- 2026-09-16: 64

## Common questions

### What is the ai.ssid/ssid-mcp server?

ai.ssid/ssid-mcp is listed in the public MCP registry as ai.ssid/ssid-mcp. Manufacturer-cited router default logins and compliance check, plus MAC/OUI vendor lookup. Free. This page covers its hosted endpoint (https://ssid.ai/mcp/http).

### Is the ai.ssid/ssid-mcp server safe to use?

ai.ssid/ssid-mcp scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the ai.ssid/ssid-mcp server expose?

ai.ssid/ssid-mcp exposes 4 tools: get_router_defaults, check_router_compliance, lookup_mac, submit_correction. Their descriptions and schemas cost roughly 608 tokens of context every time the server is loaded.

### Does the ai.ssid/ssid-mcp server require authentication?

No. We connected to ai.ssid/ssid-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ai.ssid/ssid-mcp server still maintained?

ai.ssid/ssid-mcp is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://ssid.ai/mcp/http
- Repository: https://github.com/Drumworks/ssid-mcp
- Changelog RSS feed: https://verifymcp.io/servers/ai-ssid-ssid-mcp/ssid.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-ssid-ssid-mcp/ssid.json
- HTML version of this page: https://verifymcp.io/servers/ai-ssid-ssid-mcp/ssid