# io.usefulapi/workiz (remote · workiz.usefulapi.io)

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

- Trust score: 76/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- remote · `workiz.usefulapi.io`: 76/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-workiz/workiz.md), [page](https://verifymcp.io/servers/io-usefulapi-workiz/workiz)

## Channel facts

- Endpoint: `https://workiz.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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-10-04.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 19 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-workiz 'https://workiz.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-workiz": {
      "url": "https://workiz.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-workiz": {
      "type": "http",
      "url": "https://workiz.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-workiz]
url = "https://workiz.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-workiz": {
      "type": "remote",
      "url": "https://workiz.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-workiz --url 'https://workiz.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-workiz:
    url: "https://workiz.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-workiz": {
      "Transport": "http",
      "Url": "https://workiz.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-workiz -t streamable-http -u 'https://workiz.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-workiz": {
      "type": "http",
      "url": "https://workiz.usefulapi.io/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-10-02 (score 76, +1)

- [functional] Server version: 1.3.0 → 1.5.1

### 2026-10-01 (score 75, +5)

- [security improvement] HTTPS: unverified → pass
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.3.0

### 2026-09-30 (score 70, +52)

- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [security] First check of Authorization: partial
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] 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

### 2026-09-29 (score 18)

First indexed and scored.

## MCP tools (19)

### `workiz_list_jobs` (~183 tokens)

List jobs

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 parameters:

- `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"].

### `workiz_get_job` (~66 tokens)

Get one job

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 parameters:

- `uuid` (string, required): The job's UUID (e.g. XYZ56X).

### `workiz_list_leads` (~171 tokens)

List leads

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 parameters:

- `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"].

### `workiz_get_lead` (~62 tokens)

Get one lead

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

Input parameters:

- `uuid` (string, required): The lead's UUID (e.g. XYZ56X).

### `workiz_list_team` (~57 tokens)

List team members

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/.

### `workiz_get_team_member` (~65 tokens)

Get one team member

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 parameters:

- `user_id` (string, required): The user's id, from workiz_list_team.

### `workiz_list_time_off` (~79 tokens)

List upcoming time off

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 parameters:

- `all` (boolean): Include all users' and company time off (Workiz default: false).

### `workiz_get_user_time_off` (~63 tokens)

Get a team member's time off

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

Input parameters:

- `user_name` (string, required): The team member's name as Workiz shows it, e.g. Joe Acme.

### `workiz_create_job` (~449 tokens)

Create a job

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 parameters:

- `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.

### `workiz_update_job` (~477 tokens)

Update a job

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 parameters:

- `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, required): The job's UUID (e.g. XYZ56X).
- `Unit` (string): Unit / apartment.

### `workiz_assign_job` (~91 tokens)

Assign a team member to a job

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

Input parameters:

- `UUID` (string, required): The job's UUID (e.g. XYZ56X).
- `User` (string, required): The team member's NAME exactly as Workiz shows it (e.g. Alex Wilson) — see workiz_list_team.

### `workiz_unassign_job` (~91 tokens)

Unassign a team member from a job

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

Input parameters:

- `UUID` (string, required): The job's UUID (e.g. XYZ56X).
- `User` (string, required): The team member's NAME exactly as Workiz shows it (e.g. Alex Wilson) — see workiz_list_team.

### `workiz_create_lead` (~460 tokens)

Create a lead

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 parameters:

- `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.

### `workiz_update_lead` (~454 tokens)

Update a lead

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 parameters:

- `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, required): The lead's UUID (e.g. XYZ56X).
- `Unit` (string): Unit / apartment.

### `workiz_assign_lead` (~93 tokens)

Assign a team member to a lead

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

Input parameters:

- `UUID` (string, required): The lead's UUID (e.g. XYZ56X).
- `User` (string, required): The team member's NAME exactly as Workiz shows it (e.g. Alex Wilson) — see workiz_list_team.

### `workiz_unassign_lead` (~93 tokens)

Unassign a team member from a lead

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

Input parameters:

- `UUID` (string, required): The lead's UUID (e.g. XYZ56X).
- `User` (string, required): The team member's NAME exactly as Workiz shows it (e.g. Alex Wilson) — see workiz_list_team.

### `workiz_convert_lead_to_job` (~74 tokens)

Convert a lead to a job

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 parameters:

- `UUID` (string, required): The lead's UUID (e.g. XYZ56X).

### `workiz_mark_lead_lost` (~61 tokens)

Mark a lead as lost

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

Input parameters:

- `uuid` (string, required): The lead's UUID (e.g. XYZ56X).

### `workiz_activate_lead` (~51 tokens)

Reactivate a lost lead

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

Input parameters:

- `uuid` (string, required): The lead's UUID (e.g. XYZ56X).

## Diagnostics

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

## Score history

- 2026-10-04: 76
- 2026-10-03: 76
- 2026-10-02: 76
- 2026-10-01: 75
- 2026-09-30: 70
- 2026-09-29: 18

## 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.

## Links

- Remote endpoint: https://workiz.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-workiz/workiz.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-workiz/workiz.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-workiz/workiz