Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ai.ssid/ssid-mcp

REMOTE · SSID.AI · 2 COMPONENTS

Router default logins, compliance index, MAC/OUI lookup. Reads free; submit_correction is Pro.

0 this week 77 Trust /100

Last scanned (23 hours ago)

Scores higher than 67% of remote servers

Reachable. Last reached 21 Nov 2026.

Category IoT and Hardware

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 725 tokens (~181/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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 16 Oct 26 0
    • Stability: 0.97 → pass security
  • 28 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “submit_correction” rewrote its description, which is the text the model reads security
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
    • Server version: 0.3.1 → 0.4.0 functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 17 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 16 Sept 26 0

    First indexed and scored.

Diagnostics

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 21 Nov 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 8 Nov 2026 6 Feb 2027 ECDSA 256 ECDSA-SHA384 6cba67cbd71cbf9ea99f65f1f667511d3c9
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. DS published 1814 8 Verified
ssid.ai. No DS 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
MCP tools · 4 exposed · ~643 tokens

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 →

Tool Tokens
check_router_compliance ~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.

NameTypeReqDescription
slugstringyesssid.ai router slug

No output schema declared.

No examples provided.

get_router_defaults ~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.

NameTypeReqDescription
brandstring–Manufacturer, e.g. TP-Link, Netgear, ASUS
modelstring–Model as printed on the device, e.g. Archer AX55
slugstring–ssid.ai router slug, e.g. tp-link-archer-ax55 (from ssid.ai/routers/<slug>)

No output schema declared.

No examples provided.

lookup_mac ~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.

NameTypeReqDescription
macstringyesA MAC address in any format, e.g. F4:F5:E8:11:22:33

No output schema declared.

No examples provided.

submit_correction ~177

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>. 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.

NameTypeReqDescription
fieldstringyesWhich field is wrong
proposedValuestringyesThe correct value, per the cited source
slugstringyesThe router's ssid.ai slug, e.g. 'tp-link-archer-ax55'
sourceUrlstringyesOfficial https manufacturer source confirming the correct value

No output schema declared.

No examples provided.

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.

remote · ssid.ai

# add to Claude Code
claude mcp add --transport http ai-ssid-ssid-mcp 'https://ssid.ai/mcp/http'
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. Router default logins, compliance index, MAC/OUI lookup. Reads free; submit_correction is Pro. 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 77 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 643 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the ai.ssid/ssid-mcp server?

VerifyMCP ran 12 checks on ai.ssid/ssid-mcp, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about ai.ssid/ssid-mcp: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.