Is the Ssid MCP server down?

mcp-registry/ai.ssid/ssid-mcp · v0.4.1

Also listed as glama/drumworks/ssid-mcp

healthy
Last checked 2026-10-27 16:07 UTC · handshake 609ms

As of 2026-10-27 16:07 UTC, the Ssid MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 8 minutes.

uptime (30d checks)
100%
checks observed
5,027
outages (90d)
3
tools
4

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

Point your MCP client at this streamable-http endpoint: https://ssid.ai/mcp/http

Agent-readiness: B (81/100)

B (81/100): 0 error(s), 2 warning(s) across 4 tool(s); ~955 tokens of tool definitions.
Scores higher than 33% of 15,806 MCP servers Glimind has audited.
Its tool list costs an agent ~955 tokens per session — lighter than 75% of servers.
79 → 81 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints0
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (3)

4 of 4 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: check_router_compliance, get_router_defaults, lookup_mac, submit_correction

1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: submit_correction

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 4 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fai.ssid%2Fssid-mcp/fixes

check_router_compliance 1 change
{
  "name": "check_router_compliance",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "maxLength": 120,
        "minLength": 2,
        "description": "ssid.ai router slug"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Universal default password check (UK PSTI / EU CRA pattern)"
}
get_router_defaults 1 change
{
  "name": "get_router_defaults",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "slug": {
        "type": "string",
        "maxLength": 120,
        "minLength": 2,
        "description": "ssid.ai router slug, e.g. tp-link-archer-ax55 (from ssid.ai/routers/<slug>)"
      },
      "brand": {
        "type": "string",
        "maxLength": 80,
        "minLength": 2,
        "description": "Manufacturer, e.g. TP-Link, Netgear, ASUS"
      },
      "model": {
        "type": "string",
        "maxLength": 80,
        "minLength": 2,
        "description": "Model as printed on the device, e.g. Archer AX55"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Router factory login (manufacturer-cited)"
}
lookup_mac 1 change
{
  "name": "lookup_mac",
  "description": "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 add",
  "inputSchema": {
    "type": "object",
    "required": [
      "mac"
    ],
    "properties": {
      "mac": {
        "type": "string",
        "description": "A MAC address in any format, e.g. F4:F5:E8:11:22:33"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "MAC / OUI vendor lookup"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/ai.ssid/ssid-mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/ai.ssid/ssid-mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.ssid%2Fssid-mcp.svg)](https://glimind.com/server/mcp-registry%2Fai.ssid%2Fssid-mcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fai.ssid%2Fssid-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.ssid%2Fssid-mcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.ssid%2Fssid-mcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fai.ssid%2Fssid-mcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:fb3f6e2cc5173b49…, first seen 2026-10-17, included at leaf 6567 of 80,216. Version history · verify what your client received.

Tools (4)

Compare: most reliable knowledge servers · most reliable data servers · most reliable other servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Ssid MCP server down right now?

As of 2026-10-27 16:07 UTC, the Ssid MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 8 minutes.

How many tools does Ssid MCP server provide?

Ssid MCP server advertises 4 tools, including check_router_compliance, get_router_defaults, lookup_mac, submit_correction.

How do I install Ssid MCP server?

Point your MCP client at this streamable-http endpoint: https://ssid.ai/mcp/http

Is the Ssid MCP server safe to connect to an AI agent?

Glimind scanned all 4 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Ssid MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve