Wizcom Limited
REMOTE · WIZCOMLTD.COM
Metro Detroit managed IT: company info, downtime and cyber insurance tools, AI visibility scan.
Available components
Last scanned (19 hours ago)
Scores higher than 72% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Security
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 Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability48
- 8% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1074 tokens (~63/item across 17 items; 4 tools + 13 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% of tool parameters carry a description.Partial
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 6 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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.
- 19 Nov 26 +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.
- 17 Nov 26 +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.
- 15 Nov 26 +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.
- 13 Nov 26 +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.
- 11 Nov 26 +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.
- 9 Nov 26 +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.
- 7 Nov 26 +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.
- 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
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://wizcomltd.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=wizcomltd.com | CN=WE1,O=Google Trust Services,C=US | 11 Oct 2026 | 9 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 3885ab3322e7eb3513cba1b15c8070e4 |
| SANs: wizcomltd.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of wizcomltd.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| wizcomltd.com. | DS published | 2371 | 13 | Verified |
| wizcomltd.com. | Verified address RRset verified with the apex keys |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://wizcomltd.com/mcp | Verified | 200 | |
| http (plaintext) | http://wizcomltd.com/mcp | HTTPS enforced | 301 | https://wizcomltd.com/mcp |
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_cyber_insurance_readiness Check cyber insurance readiness ~451
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.
| Name | Type | Req | Description |
|---|---|---|---|
| backup | string | yes | 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 | yes | Does every computer and server have modern security software that watches for attacks and alerts someone? |
| email_sec | string | yes | Does your email system screen out scam and phishing emails before they reach people? |
| eol | string | yes | Is everything still supported by its maker, with no old computers or software that no longer get security fixes? |
| irp | string | yes | Do you have a written plan for what to do if you're hacked, including who to call? |
| mfa_admin | string | yes | Do your admin accounts, the ones that can add users or change settings, also need the second step? |
| mfa_email | string | yes | Does everyone need a second step, like a code or a tap on their phone, to log in to work email? |
| mfa_remote | string | yes | 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 | yes | Do computers, software, and network equipment get security updates automatically or on a regular schedule? |
| payments | string | yes | 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 | yes | Have you actually restored files from your backup in the past year to prove it works? |
| training | string | yes | Does your team get cybersecurity training at least once a year, including practice phishing emails? |
No output schema declared.
No examples provided.
estimate_downtime_cost Estimate IT downtime cost ~157
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.
| Name | Type | Req | Description |
|---|---|---|---|
| revenue | number | yes | Annual revenue of the business, in US dollars. |
| salary | number | yes | Average annual salary per employee, in US dollars. |
| team | integer | yes | Number of employees who stop working when systems are down. |
No output schema declared.
No examples provided.
get_wizcom_info Get Wizcom company information ~166
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
No output schema declared.
No examples provided.
scan_ai_visibility Scan a website's AI visibility ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Website to scan, e.g. example.com or https://www.example.com. |
No output schema declared.
No examples provided.
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.
remote · wizcomltd.com
claude mcp add --transport http com-wizcomltd-wizcom 'https://wizcomltd.com/mcp'
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.