# Wizcom Limited (remote · wizcomltd.com)

Metro Detroit managed IT: company info, downtime and cyber insurance tools, AI visibility scan.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `wizcomltd.com`: 78/100 (this document), [markdown](https://verifymcp.io/servers/com-wizcomltd-wizcom/wizcomltd.md), [page](https://verifymcp.io/servers/com-wizcomltd-wizcom/wizcomltd)

## Channel facts

- Endpoint: `https://wizcomltd.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 48/100
  - 8% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1074 tokens (~63/item across 17 items; 4 tools + 13 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 94% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Wizcom Limited MCP server?

Wizcom Limited is a hosted endpoint at https://wizcomltd.com/mcp, 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.

### Claude

```bash
claude mcp add --transport http com-wizcomltd-wizcom 'https://wizcomltd.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-wizcomltd-wizcom": {
      "url": "https://wizcomltd.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-wizcomltd-wizcom": {
      "type": "http",
      "url": "https://wizcomltd.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-wizcomltd-wizcom]
url = "https://wizcomltd.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-wizcomltd-wizcom": {
      "type": "remote",
      "url": "https://wizcomltd.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-wizcomltd-wizcom --url 'https://wizcomltd.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-wizcomltd-wizcom:
    url: "https://wizcomltd.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-wizcomltd-wizcom": {
      "Transport": "http",
      "Url": "https://wizcomltd.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-wizcomltd-wizcom -t streamable-http -u 'https://wizcomltd.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-wizcomltd-wizcom": {
      "type": "http",
      "url": "https://wizcomltd.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-19 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-09 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-07 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-06 (score 71, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (4)

### `estimate_downtime_cost` (~157 tokens)

Estimate IT downtime cost

Estimate what one hour of IT downtime costs a business, from team size, average salary, and annual revenue. Returns the hourly cost broken into idle wages, lost revenue, and recovery, plus the yearly downtime cost at three levels of IT management (well-managed ~8 hours/year, typical SMB ~24 hours/year, unmanaged ~87 hours/year). Same math as the Wizcom Downtime Cost Calculator (https://wizcomltd.com/tools/downtime-calculator). Estimate only.

Input parameters:

- `revenue` (number, required): Annual revenue of the business, in US dollars.
- `salary` (number, required): Average annual salary per employee, in US dollars.
- `team` (integer, required): Number of employees who stop working when systems are down.

### `check_cyber_insurance_readiness` (~451 tokens)

Check cyber insurance readiness

Score how ready a small business is for a cyber insurance application, from 12 yes/partly/no/unsure answers about MFA, EDR, updates, backups, training, payment call-backs, and incident planning. Returns a 0-100 readiness score, a band, and a prioritized list of gaps with fixes. Same scoring as https://wizcomltd.com/tools/cyber-insurance-readiness. Educational only: not insurance or legal advice, and Wizcom is not an insurance agency.

Input parameters:

- `backup` (string, required): Do you have a backup copy that hackers couldn't reach or delete, such as one kept offline or locked in the cloud?
- `edr` (string, required): Does every computer and server have modern security software that watches for attacks and alerts someone?
- `email_sec` (string, required): Does your email system screen out scam and phishing emails before they reach people?
- `eol` (string, required): Is everything still supported by its maker, with no old computers or software that no longer get security fixes?
- `irp` (string, required): Do you have a written plan for what to do if you're hacked, including who to call?
- `mfa_admin` (string, required): Do your admin accounts, the ones that can add users or change settings, also need the second step?
- `mfa_email` (string, required): Does everyone need a second step, like a code or a tap on their phone, to log in to work email?
- `mfa_remote` (string, required): When anyone logs in to your systems from outside the office, is that second step required? Use "na" if nobody logs in remotely.
- `patch` (string, required): Do computers, software, and network equipment get security updates automatically or on a regular schedule?
- `payments` (string, required): Before sending a wire or changing someone's bank details, do you call them at a phone number you already have? Use "na" if not applicable.
- `restore` (string, required): Have you actually restored files from your backup in the past year to prove it works?
- `training` (string, required): Does your team get cybersecurity training at least once a year, including practice phishing emails?

### `scan_ai_visibility` (~97 tokens)

Scan a website's AI visibility

Run a free 5-check scan of a website's AI/agent-readiness basics: robots.txt, sitemap.xml, llms.txt, .well-known/security.txt, and homepage JSON-LD. Returns a score out of 5 with a pass/fail detail per check. Limited to 20 scans per hour per visitor.

Input parameters:

- `url` (string, required): Website to scan, e.g. example.com or https://www.example.com.

### `get_wizcom_info` (~166 tokens)

Get Wizcom company information

Get information about Wizcom Limited, a Metro Detroit managed IT provider, as Markdown from wizcomltd.com. Topics: overview, company (history, team), services (list), service (one service: pass slug), service_area (list), location (one city/county page: pass slug, e.g. "troy" or "macomb-county"), contact, site_index (every page).

Input parameters:

- `slug` (string): For topic "service": one of managed-it-services, cloud-solutions, web-app-development, network-infrastructure, it-consulting, voip-unified-communications. For topic "location": a service-area page sl…
- `topic` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-wizcomltd-wizcom/wizcomltd#diagnostics

## Score history

- 2026-11-21: 78
- 2026-11-20: 78
- 2026-11-19: 78
- 2026-11-18: 77
- 2026-11-17: 77
- 2026-11-16: 76
- 2026-11-15: 76
- 2026-11-14: 75
- 2026-11-13: 75
- 2026-11-12: 74
- 2026-11-11: 74
- 2026-11-10: 73
- 2026-11-09: 73
- 2026-11-08: 72
- 2026-11-07: 72
- 2026-11-06: 71
- 2026-11-05: 71
- 2026-11-04: 71
- 2026-11-03: 70
- 2026-11-02: 70
- 2026-11-01: 69
- 2026-10-31: 69
- 2026-10-30: 68
- 2026-10-29: 68
- 2026-10-28: 67

## Common questions

### What is the Wizcom Limited MCP server?

Wizcom Limited is an MCP server listed in the public MCP registry as com.wizcomltd/wizcom. Metro Detroit managed IT: company info, downtime and cyber insurance tools, AI visibility scan. This page covers its hosted endpoint (https://wizcomltd.com/mcp).

### Is the Wizcom Limited MCP server safe to use?

Wizcom Limited scores 78 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 Wizcom Limited MCP server expose?

Wizcom Limited exposes 4 tools: estimate_downtime_cost, check_cyber_insurance_readiness, scan_ai_visibility, get_wizcom_info. Their descriptions and schemas cost roughly 871 tokens of context every time the server is loaded.

### Does the Wizcom Limited MCP server require authentication?

No. We connected to Wizcom Limited without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Wizcom Limited MCP server still maintained?

Wizcom Limited 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 Wizcom Limited MCP server?

VerifyMCP ran 13 checks on Wizcom Limited, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.

## Links

- Remote endpoint: https://wizcomltd.com/mcp
- Website: https://wizcomltd.com/developers.md
- Changelog RSS feed: https://verifymcp.io/servers/com-wizcomltd-wizcom/wizcomltd.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-wizcomltd-wizcom/wizcomltd/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-wizcomltd-wizcom/wizcomltd.json
- HTML version of this page: https://verifymcp.io/servers/com-wizcomltd-wizcom/wizcomltd
