ssid-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SSID_API_KEY | No | Optional API key to raise rate limits. Get one at https://ssid.ai/api-docs | |
| SSID_API_BASE | No | Base URL for the ssid.ai API. Defaults to the official API. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_router_defaultsA | 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. |
| check_router_complianceA | 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. |
| lookup_macA | 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. |
| submit_correctionA | 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/. Requires an ssid Pro key ($15/mo, ssid.ai/pricing) sent as SSID_API_KEY or a Bearer token; the three read tools stay free. |
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 4 tools
Each tool has a clearly distinct purpose: router default credentials, regulatory compliance status, MAC vendor identification, and a correction submission. The only mild overlap is that get_router_defaults and check_router_compliance both hinge on 'credential type', so an agent must read descriptions carefully to pick the right one, but the descriptions make the boundary explicit (credentials vs. compliance index).
All four tools follow a clean snake_case verb_noun pattern: get_router_defaults, check_router_compliance, lookup_mac, submit_correction. No mixed conventions or vague verbs.
Four tools is well-scoped for a narrow domain (router defaults, compliance, MAC lookup, corrections). Each tool earns its place with a distinct capability and no redundancy.
The set covers the read surface (router defaults, compliance, MAC) plus a write path (submit_correction), forming a coherent lifecycle. The lack of any listing/wildcard search for routers (explicitly excluded from get_router_defaults) is a minor gap, since agents must already know a slug or brand+model.