ai.ssid/ssid-mcp
REMOTE · SSID.AI · 2 COMPONENTS · SCANNED SEP 22
Manufacturer-cited router default logins and compliance check, plus MAC/OUI vendor lookup. Free.
Available components
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · ssid.ai
claude mcp add --transport http ai-ssid-ssid-mcp 'https://ssid.ai/mcp/http'
{
"mcpServers": {
"ai-ssid-ssid-mcp": {
"url": "https://ssid.ai/mcp/http"
}
}
} {
"servers": {
"ai-ssid-ssid-mcp": {
"type": "http",
"url": "https://ssid.ai/mcp/http"
}
}
} [mcp_servers.ai-ssid-ssid-mcp] url = "https://ssid.ai/mcp/http"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-ssid-ssid-mcp": {
"type": "remote",
"url": "https://ssid.ai/mcp/http",
"enabled": true
}
}
} openclaw mcp add ai-ssid-ssid-mcp --url 'https://ssid.ai/mcp/http' --transport streamable-http
mcp_servers:
ai-ssid-ssid-mcp:
url: "https://ssid.ai/mcp/http" {
"McpServers": {
"ai-ssid-ssid-mcp": {
"Transport": "http",
"Url": "https://ssid.ai/mcp/http"
}
}
} assistant mcp add ai-ssid-ssid-mcp -t streamable-http -u 'https://ssid.ai/mcp/http'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 +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.
- 18 Sept 26 +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.
- 17 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 16 Sept 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Probed https://ssid.ai/mcp/http
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ssid.ai | CN=YE1,O=Let's Encrypt,C=US | 9 Sept 2026 | 8 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5e90f7e893225dde18fe5e4622a3aeae44f |
| SANs: ssid.ai, www.ssid.ai | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ssid.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| ssid.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ssid.ai/mcp/http | Verified | 200 | |
| http (plaintext) | http://ssid.ai/mcp/http | HTTPS enforced | 301 | https://ssid.ai/mcp/http |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_router_compliance Universal default password check (UK PSTI / EU CRA pattern) ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | ssid.ai router slug |
No output schema declared.
No examples provided.
get_router_defaults Router factory login (manufacturer-cited) ~180
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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>) |
No output schema declared.
No examples provided.
lookup_mac MAC / OUI vendor lookup ~187
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.
| Name | Type | Req | Description |
|---|---|---|---|
| mac | string | yes | A MAC address in any format, e.g. F4:F5:E8:11:22:33 |
No output schema declared.
No examples provided.
submit_correction Propose a router default-login correction ~142
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>.
| Name | Type | Req | Description |
|---|---|---|---|
| field | string | yes | Which field is wrong |
| proposedValue | string | yes | The correct value, per the cited source |
| slug | string | yes | The router's ssid.ai slug, e.g. 'tp-link-archer-ax55' |
| sourceUrl | string | yes | Official https manufacturer source confirming the correct value |
No output schema declared.
No examples provided.
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.