wizcom
Registry code: 23be303a455dd6e5
Wizcom Limited is a managed IT services provider in Metro Detroit, Michigan (founded 1983). Use get_wizcom_info for company, service, service-area, and contact details. estimate_downtime_cost and check_cyber_insurance_readiness are free self-assessment calculators; scan_ai_visibility checks any website's AI-readiness basics. This server cannot submit contact requests, quotes, or support tickets: direct people to https://wizcomltd.com/contact or [email protected].
- endpoint
- https://wizcomltd.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is wizcom live?
- Yes — it answered the hub's last check (checked 49m ago). It answered 100% of checks over the last 30 days.
- Is wizcom free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does wizcom have?
- 4 tools: scan_ai_visibility, get_wizcom_info, check_cyber_insurance_readiness, estimate_downtime_cost.
- Is wizcom safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 4 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
scan_ai_visibility unknown 49m ago
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.
{ "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "description": "Website to scan, e.g. example.com or https://www.example.com." } } }arguments 12 linesget_wizcom_info unknown 27h ago
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).
{ "type": "object", "required": [ "topic" ], "properties": { "slug": { "type": "string", "description": "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 slug such as troy, warren, or oakland-county." }, "topic": { "enum": [ "overview", "company", "services", "service", "service_area", "location", "contact", "site_index" ], "type": "string" } } }arguments 25 linescheck_cyber_insurance_readiness unknown 49m ago
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.
{ "type": "object", "required": [ "mfa_email", "mfa_remote", "mfa_admin", "edr", "patch", "eol", "backup", "restore", "email_sec", "training", "payments", "irp" ], "properties": { "edr": { "enum": [ "yes", "partly", "no", "unsure" ], "type": "string", "description": "Does every computer and server have modern security software that watches for attacks and alerts someone?" }, "eol": { "enum": [ "yes", "partly", "no", "unsure" ], "type": "string", "description": "Is everything still supported by its maker, with no old computers or software that no longer get security fixes?" }, "irp": { "enum": [ "yes", "partly", "no", "unsure" ], "type": "string", "description": "Do you have a written plan for what to do if you're hacked, including who to call?" }, "patch": { "enum": [ "yes", "partly", "no", "unsure" ], "type": "string", "description": "Do computers, software, and network equipment get security updates automatically or on a regular schedule?" }, "backup": { "enum": [ "yes", "partly", "no", "unsure" ], "type": "string", "description": "Do you have a backup copy that hackers couldn't reach or delete, such as one kept offline or locked in the cloud?" }, "restore": { "enum": [ "yes", "partly", "no", "unsure" ], "type": "string", "description": "Have you actually restored files from your backup in the past year to prove it works?" }, "payments": { "enum": [ "yes", "partly", "no", "unsure", "na" ], "type": "string", "description": "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." }, "training": { "enum": [ "yes", "partly", "no", "unsure" ], "type": "string", "description": "Does your team get cybersecurity training at least once a year, including practice phishing emails?" }, "email_sec": { "enum": [ "yes", "partly", "no", "unsure" ], "type": "string", "description": "Does your email system screen out scam and phishing emails before they reach people?" }, "mfa_admin": { "enum": [ "yes", "partly", "no", "unsure" ], "type": "string", "description": "Do your admin accounts, the ones that can add users or change settings, also need the second step?" }, "mfa_email": { "enum": [ "yes", "partly", "no", "unsure" ], "type": "string", "description": "Does everyone need a second step, like a code or a tap on their phone, to log in to work email?" }, "mfa_remote": { "enum": [ "yes", "partly", "no", "unsure", "na" ], "type": "string", "description": "When anyone logs in to your systems from outside the office, is that second step required? Use \"na\" if nobody logs in remotely." } } }arguments 141 linesestimate_downtime_cost unknown 49m ago
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.
{ "type": "object", "required": [ "team", "salary", "revenue" ], "properties": { "team": { "type": "integer", "maximum": 100000, "minimum": 1, "description": "Number of employees who stop working when systems are down." }, "salary": { "type": "number", "maximum": 10000000, "minimum": 10000, "description": "Average annual salary per employee, in US dollars." }, "revenue": { "type": "number", "maximum": 10000000000, "minimum": 10000, "description": "Annual revenue of the business, in US dollars." } } }arguments 28 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id23be303a455dd6e5.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/23be303a455dd6e5/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/23be303a455dd6e5?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.