How do I install the io.usefulapi/workiz MCP server?

io.usefulapi/workiz is a hosted endpoint at https://workiz.usefulapi.io/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.

io.usefulapi/workiz

REMOTE · WORKIZ.USEFULAPI.IO · SCANNED OCT 4

Manage Workiz jobs and leads: create, update, assign team members and convert leads to jobs.

Available components

remote · workiz.usefulapi.io 76

76 76 Trust /100

Trust breakdown (7 categories)

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 Security89

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability70

AI-judged instruction clarity (excellent).Pass
Context-footprint check failed: tool/resource definitions use about 3140 tokens (~165/item across 19 items; 19 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management13

Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Tool Safety100

No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass

Capabilities60

Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Changelog

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.

2 Oct 26 +1
- Server version: 1.3.0 → 1.5.1 functional
1 Oct 26 +5
- HTTPS: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.3.0 functional
30 Sept 26 +52
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
29 Sept 26 18

First indexed and scored.

Show 1 earlier entry Hide earlier entries

Diagnostics

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 4 Oct 2026 · Probed https://workiz.usefulapi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=usefulapi.io	CN=WE1,O=Google Trust Services,C=US	13 Sept 2026	12 Dec 2026	ECDSA 256	ECDSA-SHA256	d9be3287b0fde9630e825ba1f79bff3f
SANs: usefulapi.io, *.usefulapi.io
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 insecure

Validation of workiz.usefulapi.io. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
io.	present	57355	8	Verified
usefulapi.io.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result	Enforced and verified
Enforced	On tool calls
HTTP status	200

WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://workiz.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Bearer realm="OAuth", resource_metadata="https://workiz.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Protected resource metadata

Document	https://workiz.usefulapi.io/.well-known/oauth-protected-resource/mcp
Retrieved	Yes
Resource	https://workiz.usefulapi.io/mcp
Authorisation server	https://workiz.usefulapi.io

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://workiz.usefulapi.io/mcp	Verified	200
http (plaintext)	http://workiz.usefulapi.io/mcp	HTTPS enforced	301	https://workiz.usefulapi.io/mcp

MCP tools · 19 exposed · ~3,140 tokens

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 →

Tool Tokens

workiz_activate_lead Reactivate a lost lead ~51

WRITE: change a lost lead back to active. Workiz: POST /lead/activate/{UUID}/.

Input Output Examples

Name	Type	Req	Description
uuid	string	yes	The lead's UUID (e.g. XYZ56X).

No output schema declared.

No examples provided.

workiz_assign_job Assign a team member to a job ~91

WRITE: assign a team member (by name) to a job. Reversible with workiz_unassign_job. Workiz: POST /job/assign/.

Input Output Examples

Name	Type	Req	Description
UUID	string	yes	The job's UUID (e.g. XYZ56X).
User	string	yes	The team member's NAME exactly as Workiz shows it (e.g. Alex Wilson) — see workiz_list_team.

No output schema declared.

No examples provided.

workiz_assign_lead Assign a team member to a lead ~93

WRITE: assign a team member (by name) to a lead. Reversible with workiz_unassign_lead. Workiz: POST /lead/assign/.

Input Output Examples

Name	Type	Req	Description
UUID	string	yes	The lead's UUID (e.g. XYZ56X).
User	string	yes	The team member's NAME exactly as Workiz shows it (e.g. Alex Wilson) — see workiz_list_team.

No output schema declared.

No examples provided.

workiz_convert_lead_to_job Convert a lead to a job ~74

WRITE (no API undo): convert a lead into a job. Creates a new job from the lead and returns its UUID and link; the API cannot reverse the conversion. Workiz: POST /lead/convert/.

Input Output Examples

Name	Type	Req	Description
UUID	string	yes	The lead's UUID (e.g. XYZ56X).

No output schema declared.

No examples provided.

workiz_create_job Create a job ~449

WRITE: create a new job (schedule, client contact and address, type, source, notes). Returns the new job's UUID, ClientId and app link. Workiz: POST /job/create/.

Input Output Examples

Name	Type	Req	Description
Address	string	–	Street address, e.g. 123 W Main Street.
City	string	–	City.
ClientId	integer	–	Existing Workiz client id to attach this to.
Company	string	–	Client company name.
Country	string	–	Country code, e.g. US.
Created	string	–	Creation timestamp to record. Date-time string, e.g. 2026-10-01T09:00:00.000Z.
CreatedBy	string	–	Name recorded as the creator.
Email	string	–	Client email.
FirstName	string	–	Client first name.
JobDateTime	string	–	Scheduled start. Date-time string, e.g. 2026-10-01T09:00:00.000Z.
JobEndDateTime	string	–	Scheduled end. Date-time string, e.g. 2026-10-01T09:00:00.000Z.
JobNotes	string	–	Internal job notes.
JobSource	string	–	Lead/job source, e.g. Google.
JobType	string	–	Job type, e.g. Repair.
LastName	string	–	Client last name.
Phone	string	–	Primary phone, digits only, e.g. 6195555555.
PhoneExt	string	–	Primary phone extension.
PostalCode	string	–	Postal / ZIP code.
ReferralCompany	string	–	Referral company, e.g. Thumbtack.
SecondPhone	string	–	Secondary phone.
SecondPhoneExt	string	–	Secondary phone extension.
ServiceArea	string	–	Service area, e.g. metro1.
State	string	–	State, e.g. CA.
Timezone	string	–	Timezone, e.g. US/Pacific.
Unit	string	–	Unit / apartment.

No output schema declared.

No examples provided.

workiz_create_lead Create a lead ~460

WRITE: create a new lead (client contact and address, requested time, job type, source, notes). Returns the new lead's UUID, ClientId and app link. Workiz: POST /lead/create/.

Input Output Examples

Name	Type	Req	Description
Address	string	–	Street address, e.g. 123 W Main Street.
City	string	–	City.
ClientId	integer	–	Existing Workiz client id to attach this to.
Company	string	–	Client company name.
Country	string	–	Country code, e.g. US.
Created	string	–	Creation timestamp to record. Date-time string, e.g. 2026-10-01T09:00:00.000Z.
CreatedBy	string	–	Name recorded as the creator.
Email	string	–	Client email.
FirstName	string	–	Client first name.
JobSource	string	–	Lead/job source, e.g. Google.
JobType	string	–	Job type, e.g. Repair.
LastName	string	–	Client last name.
LeadDateTime	string	–	Scheduled start of the lead appointment. Date-time string, e.g. 2026-10-01T09:00:00.000Z.
LeadEndDateTime	string	–	Scheduled end of the lead appointment. Date-time string, e.g. 2026-10-01T09:00:00.000Z.
LeadNotes	string	–	Internal lead notes.
Phone	string	–	Primary phone, digits only, e.g. 6195555555.
PhoneExt	string	–	Primary phone extension.
PostalCode	string	–	Postal / ZIP code.
ReferralCompany	string	–	Referral company, e.g. Thumbtack.
SecondPhone	string	–	Secondary phone.
SecondPhoneExt	string	–	Secondary phone extension.
ServiceArea	string	–	Service area, e.g. metro1.
State	string	–	State, e.g. CA.
Timezone	string	–	Timezone, e.g. US/Pacific.
Unit	string	–	Unit / apartment.

No output schema declared.

No examples provided.

workiz_get_job Get one job ~66

Fetch one job by UUID: schedule, status, client contact and address, totals and amount due, notes, tags and assigned team. Workiz: GET /job/get/{UUID}/.

Input Output Examples

Name	Type	Req	Description
uuid	string	yes	The job's UUID (e.g. XYZ56X).

No output schema declared.

No examples provided.

workiz_get_lead Get one lead ~62

Fetch one lead by UUID: schedule, status, client contact and address, source, notes and assigned team. Workiz: GET /lead/get/{UUID}/.

Input Output Examples

Name	Type	Req	Description
uuid	string	yes	The lead's UUID (e.g. XYZ56X).

No output schema declared.

No examples provided.

workiz_get_team_member Get one team member ~65

Fetch one team member by user id: name, role, field-tech flag, email, service areas, skills and active status. Workiz: GET /team/get/{USER_ID}.

Input Output Examples

Name	Type	Req	Description
user_id	string	yes	The user's id, from workiz_list_team.

No output schema declared.

No examples provided.

workiz_get_user_time_off Get a team member's time off ~63

List one team member's FUTURE time off, by their name. Workiz: GET /TimeOff/get/{USER_NAME}.

Input Output Examples

Name	Type	Req	Description
user_name	string	yes	The team member's name as Workiz shows it, e.g. Joe Acme.

No output schema declared.

No examples provided.

workiz_list_jobs List jobs ~183

List jobs, most recently scheduled first (sorted by JobDateTime, descending). Filter by start date, open-only, and status; page with offset/records (max 100). Without start_date Workiz returns the last 14 days. Workiz: GET /job/all/.

Input Output Examples

Name	Type	Req	Description
offset	integer	–	Record offset for paging (default 0).
only_open	boolean	–	Only open records, excluding Done and Canceled statuses (Workiz default: true).
records	integer	–	Number of records to return, 1-100 (default 100).
start_date	string	–	Return records from this date (yyyy-MM-dd) until today. For jobs, Workiz defaults to the last 14 days when omitted.
status	array	–	Only these statuses, e.g. ["Submitted", "In progress"].

No output schema declared.

No examples provided.

workiz_list_leads List leads ~171

List leads, most recent first (sorted by LeadDateTime, descending). Filter by start date, open-only, and status; page with offset/records (max 100). Workiz: GET /lead/all/.

Input Output Examples

Name	Type	Req	Description
offset	integer	–	Record offset for paging (default 0).
only_open	boolean	–	Only open records, excluding Done and Canceled statuses (Workiz default: true).
records	integer	–	Number of records to return, 1-100 (default 100).
start_date	string	–	Return records from this date (yyyy-MM-dd) until today. For jobs, Workiz defaults to the last 14 days when omitted.
status	array	–	Only these statuses, e.g. ["Submitted", "In progress"].

No output schema declared.

No examples provided.

workiz_list_team List team members ~57

List the account's active team members: id, name, role, whether they are a field tech, email, service areas and skills. Use the name to assign people to jobs or leads. Workiz: GET /team/all/.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

workiz_list_time_off List upcoming time off ~79

List FUTURE time off (start, end, userName — 'Entire Business' for company-wide closures). Set all=true to include every user and company time off. Useful before scheduling. Workiz: GET /TimeOff/get/.

Input Output Examples

Name	Type	Req	Description
all	boolean	–	Include all users' and company time off (Workiz default: false).

No output schema declared.

No examples provided.

workiz_mark_lead_lost Mark a lead as lost ~61

WRITE: mark a lead as lost. Reversible with workiz_activate_lead. Workiz: POST /lead/markLost/{UUID}/.

Input Output Examples

Name	Type	Req	Description
uuid	string	yes	The lead's UUID (e.g. XYZ56X).

No output schema declared.

No examples provided.

workiz_unassign_job Unassign a team member from a job ~91

WRITE: remove a team member (by name) from a job. Reversible with workiz_assign_job. Workiz: POST /job/unassign/.

Input Output Examples

Name	Type	Req	Description
UUID	string	yes	The job's UUID (e.g. XYZ56X).
User	string	yes	The team member's NAME exactly as Workiz shows it (e.g. Alex Wilson) — see workiz_list_team.

No output schema declared.

No examples provided.

workiz_unassign_lead Unassign a team member from a lead ~93

WRITE: remove a team member (by name) from a lead. Reversible with workiz_assign_lead. Workiz: POST /lead/unassign/.

Input Output Examples

Name	Type	Req	Description
UUID	string	yes	The lead's UUID (e.g. XYZ56X).
User	string	yes	The team member's NAME exactly as Workiz shows it (e.g. Alex Wilson) — see workiz_list_team.

No output schema declared.

No examples provided.

workiz_update_job Update a job ~477

WRITE: update fields on an existing job — status/sub-status, reschedule (JobDateTime/JobEndDateTime), contact, address, type, source, notes, tags. Only the fields you pass are sent. Workiz: POST /job/update/.

Input Output Examples

Name	Type	Req	Description
Address	string	–	Street address, e.g. 123 W Main Street.
City	string	–	City.
ClientId	integer	–	Existing Workiz client id to attach this to.
Company	string	–	Client company name.
Country	string	–	Country code, e.g. US.
CreatedBy	string	–	Name recorded as the creator.
Email	string	–	Client email.
FirstName	string	–	Client first name.
JobDateTime	string	–	New scheduled start. Date-time string, e.g. 2026-10-01T09:00:00.000Z.
JobEndDateTime	string	–	New scheduled end. Date-time string, e.g. 2026-10-01T09:00:00.000Z.
JobNotes	string	–	Internal job notes.
JobSource	string	–	Lead/job source, e.g. Google.
JobType	string	–	Job type, e.g. Repair.
LastName	string	–	Client last name.
Phone	string	–	Primary phone, digits only, e.g. 6195555555.
PhoneExt	string	–	Primary phone extension.
PostalCode	string	–	Postal / ZIP code.
SecondPhone	string	–	Secondary phone.
SecondPhoneExt	string	–	Secondary phone extension.
ServiceArea	string	–	Service area, e.g. metro1.
State	string	–	State, e.g. CA.
Status	string	–	New job status, e.g. "In progress".
SubStatus	string	–	New job sub-status.
Tags	array	–	Job tags, e.g. ["estimate", "callback"].
Timezone	string	–	Timezone, e.g. US/Pacific.
UUID	string	yes	The job's UUID (e.g. XYZ56X).
Unit	string	–	Unit / apartment.

No output schema declared.

No examples provided.

workiz_update_lead Update a lead ~454

WRITE: update fields on an existing lead — status, schedule, contact, address, type, source, notes, tags. Only the fields you pass are sent. Workiz: POST /lead/update/.

Input Output Examples

Name	Type	Req	Description
Address	string	–	Street address, e.g. 123 W Main Street.
City	string	–	City.
ClientId	integer	–	Existing Workiz client id to attach this to.
Company	string	–	Client company name.
Country	string	–	Country code, e.g. US.
CreatedBy	string	–	Name recorded as the creator.
Email	string	–	Client email.
FirstName	string	–	Client first name.
JobSource	string	–	Lead/job source, e.g. Google.
JobType	string	–	Job type, e.g. Repair.
LastName	string	–	Client last name.
LeadDateTime	string	–	New scheduled start. Date-time string, e.g. 2026-10-01T09:00:00.000Z.
LeadEndDateTime	string	–	New scheduled end. Date-time string, e.g. 2026-10-01T09:00:00.000Z.
LeadNotes	string	–	Internal lead notes.
Phone	string	–	Primary phone, digits only, e.g. 6195555555.
PhoneExt	string	–	Primary phone extension.
PostalCode	string	–	Postal / ZIP code.
SecondPhone	string	–	Secondary phone.
SecondPhoneExt	string	–	Secondary phone extension.
ServiceArea	string	–	Service area, e.g. metro1.
State	string	–	State, e.g. CA.
Status	string	–	New lead status, e.g. "In progress".
Tags	array	–	Lead tags, e.g. ["estimate", "callback"].
Timezone	string	–	Timezone, e.g. US/Pacific.
UUID	string	yes	The lead's UUID (e.g. XYZ56X).
Unit	string	–	Unit / apartment.

No output schema declared.

No examples provided.

Common questions

What is the io.usefulapi/workiz MCP server?

io.usefulapi/workiz is an MCP server listed in the public MCP registry as io.usefulapi/workiz. Manage Workiz jobs and leads: create, update, assign team members and convert leads to jobs. This page covers its hosted endpoint (https://workiz.usefulapi.io/mcp).

Is the io.usefulapi/workiz MCP server safe to use?

io.usefulapi/workiz scores 76 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 io.usefulapi/workiz MCP server expose?

io.usefulapi/workiz exposes 19 tools: workiz_list_jobs, workiz_get_job, workiz_list_leads, workiz_get_lead, workiz_list_team, and 14 more. Their descriptions and schemas cost roughly 3,140 tokens of context every time the server is loaded.

Does the io.usefulapi/workiz MCP server require authentication?

Yes. io.usefulapi/workiz asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the io.usefulapi/workiz MCP server still maintained?

io.usefulapi/workiz is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Badge

Put this score in your README. The image is served from a stable URL, updates when the score does, and links back to the evidence on this page. It shows nothing that is not already published here.

Score Verified Plain

The two-cell badge: our name, and this channel's current score out of 100.

Markdown

 [![VerifyMCP trust score for io.usefulapi/workiz](https://verifymcp.io/badge/io-usefulapi-workiz/workiz.svg)](https://verifymcp.io/servers/io-usefulapi-workiz/workiz)

HTML

 <a href="https://verifymcp.io/servers/io-usefulapi-workiz/workiz"><img src="https://verifymcp.io/badge/io-usefulapi-workiz/workiz.svg" alt="VerifyMCP trust score for io.usefulapi/workiz" height="20"></a>

A single cell stating that the server is listed here. Carries no number.

Markdown

 [![VerifyMCP trust score for io.usefulapi/workiz](https://verifymcp.io/badge/io-usefulapi-workiz/workiz.svg?variant=verified)](https://verifymcp.io/servers/io-usefulapi-workiz/workiz)

HTML

 <a href="https://verifymcp.io/servers/io-usefulapi-workiz/workiz"><img src="https://verifymcp.io/badge/io-usefulapi-workiz/workiz.svg?variant=verified" alt="VerifyMCP trust score for io.usefulapi/workiz" height="20"></a>

The score alone, tier-coloured, for a badge row that is already crowded.

Markdown

 [![VerifyMCP trust score for io.usefulapi/workiz](https://verifymcp.io/badge/io-usefulapi-workiz/workiz.svg?variant=plain)](https://verifymcp.io/servers/io-usefulapi-workiz/workiz)

HTML

 <a href="https://verifymcp.io/servers/io-usefulapi-workiz/workiz"><img src="https://verifymcp.io/badge/io-usefulapi-workiz/workiz.svg?variant=plain" alt="VerifyMCP trust score for io.usefulapi/workiz" height="20"></a>

Score history · last 30 days

29 Sept 4 Oct