ssid.ai MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Manufacturer-cited router factory-login and MAC vendor tools: Do manufacturer citations and correction review remain current without implying permission to access a router?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Router default-credential/compliance and MAC/OUI manufacturer intelligence.

What we know

Free MCP for manufacturer-cited router factory login/reset data, universal-default-password compliance checks, MAC/OUI vendor resolution with randomized-address detection, plus a Pro correction-submission tool.

Maintenance / activity evidence

ssid-mcp 0.4.1 published 2026-10-05T05:41:20.905Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Mostly public read lookup; Pro correction creates a review request. Writes: Submit correction proposal.
Optional API key.
Sensitive access: Potential local network identifiers/MAC addresses

Low authority; MAC addresses can still be sensitive network identifiers.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do manufacturer citations and correction review remain current without implying permission to access a router?

The bounded review of the publisher's documented Manufacturer-cited router factory-login and MAC vendor tools and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Low authority; MAC addresses can still be sensitive network identifiers.
Mostly public read lookup; Pro correction creates a review request.
Optional API key.
Queries go to ssid.ai; MAC/router data is public/manufacturer/IEEE-derived.
Reviewed write actions: Submit correction proposal
Sensitive access: Potential local network identifiers/MAC addresses
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Router compliance output is documentation-based, not legal advice.
Randomized/private MACs intentionally return no vendor.
Correction submission is a write workflow and requires Pro.
Router rate limits apply.

Original activity observations

ssid-mcp 0.4.1 published 2026-10-05T05:41:20.905Z

Technical identity

npm/ssid-mcp

Exact implementation source: https://www.npmjs.com/package/ssid-mcp ↗
Reviewed resource type: MCP Server
Repository identity: Drumworks/ssid-mcp
Package identity: npm:ssid-mcp
Service endpoint: https://ssid.ai/mcp/http

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry metadata ↗
ssid-mcp
Recorded package identity, distribution or download evidence.
GitHub repository ↗
drumworks/ssid-mcp
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.
Evidence source ↗
ssid.ai/api-docs
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
ssid.ai/pricing
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher-documented package/connection route; replace placeholders and verify host-specific syntax.
Publisher setup example · Publisher instructions
npx -y ssid-mcp
Configure / authenticate
MCP100 setup guide
Publisher config via mcpServers; optional SSID_API_KEY for metered/paid features and SSID_API_BASE when using custom API.
Use correct transport and published host config. Never paste secrets in chat; server registration is separate from software installation.
Environment settings: SSID_API_KEY (optional/free or Pro), SSID_API_BASE (optional)
Previously reviewed configuration / prerequisites: Node 18+
Previously reviewed configuration / prerequisites: Read tools need no key; correction requires Pro key.
Check connection
Suggested check
Confirm tool discovery and a read-only availability/status lookup if provided.
Remove / uninstall / revoke
MCP100 setup guide
If registered as `ssid-mcp` in Claude Code, remove its exact client entry with `claude mcp remove ssid-mcp`; for Cursor/Claude Desktop/Codex, remove the matching MCP entry in that host settings. This client removal is MCP100-composed, not a vendor uninstall instruction. Npx does not imply a global install; do not delete user data or revoke credentials implicitly.
Conditional host / package cleanup · Claude Code only · MCP100 composed guide
claude mcp remove ssid-mcp

Official Documentation & Sources

What it does

Free MCP for manufacturer-cited router factory login/reset data, universal-default-password compliance checks, MAC/OUI vendor resolution with randomized-address detection, plus a Pro correction-submission tool.

Capability: Security & Testing
Resource type: MCP Server
Industry: Cybersecurity
Best fit: Router default-credential/compliance and MAC/OUI manufacturer intelligence.

Representative uses

Look up router factory login/reset details
Check UK PSTI/EU CRA default-password pattern
Resolve MAC/OUI manufacturer
Submit cited data correction on Pro

Limitations

Router compliance output is documentation-based, not legal advice.
Randomized/private MACs intentionally return no vendor.
Correction submission is a write workflow and requires Pro.
Router rate limits apply.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Optional API key.
Permissions: Mostly public read lookup; Pro correction creates a review request.
Data handling: Queries go to ssid.ai; MAC/router data is public/manufacturer/IEEE-derived.
Cost: freemium
Risk and cautions: Low authority; MAC addresses can still be sensitive network identifiers.

Access scope and cautions

Write actions: Submit correction proposal
Sensitive access: Potential local network identifiers/MAC addresses
Risk level: low

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Look up router factory login/reset details; Check UK PSTI/EU CRA default-password pattern; Resolve MAC/OUI manufacturer; Submit cited data correction on Pro.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y ssid-mcp. Recorded endpoint: https://ssid.ai/mcp/http. Recorded transport: stdio, streamable_http. Recorded environment-variable notes: SSID_API_KEY (optional/free or Pro); SSID_API_BASE (optional). No configuration values are supplied here. Prerequisites: Node 18+; MCP client. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Read tools need no key; correction requires Pro key.

Can it modify data or perform write operations?

Documented write actions include: Submit correction proposal. Recorded permission boundary: Mostly public read lookup; Pro correction creates a review request.

What data-handling boundary should I consider?

Queries go to ssid.ai; MAC/router data is public/manufacturer/IEEE-derived. Recorded sensitive-access context: Potential local network identifiers/MAC addresses.

What limitations and risks should I check before use?

Low authority; MAC addresses can still be sensitive network identifiers. Router compliance output is documentation-based, not legal advice. Randomized/private MACs intentionally return no vendor. Correction submission is a write workflow and requires Pro. Router rate limits apply. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.