Workiz MCP by usefulapi
io.usefulapi/workizusefulapi.iostreamable-httpv1.40.4Scanned
Manage Workiz jobs and leads: create, update, assign team members and convert leads to jobs.
19 tools: 11 can delete or cancel things and 8 only read.
- Reads private data · 4
- Reads text others write · 2
- Can send data out · 0
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
11 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Workiz MCP by usefulapi can do
The Workiz MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 19 tools. It can delete or cancel things (11 tools: workiz_create_job, workiz_update_job, workiz_assign_job, workiz_unassign_job and 7 more). 8 tools only read.
4 tools read private data (workiz_get_job, workiz_get_lead, workiz_list_team and 1 more); 2 tools bring in text other people can write (workiz_list_team and workiz_get_team_member).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.40.4.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
19 tools
Deletes or cancels 11Claude Code: deny
workiz_activate_leadWRITE: change a lost lead back to active.No findings
Why it is in this group
- The description's first verb is "write": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it WRITE: change a lost lead back to active. Workiz: POST /lead/activate/{UUID}/.
Annotations the server declares
- title: Reactivate a lost lead
- destructiveHint: true
workiz_assign_jobWRITE: assign a team member (by name) to a job.No findings
Why it is in this group
- The name "workiz_assign_job" says "assign": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it WRITE: assign a team member (by name) to a job. Reversible with workiz_unassign_job. Workiz: POST /job/assign/.
Annotations the server declares
- title: Assign a team member to a job
- destructiveHint: true
workiz_assign_leadWRITE: assign a team member (by name) to a lead.No findings
Why it is in this group
- The name "workiz_assign_lead" says "assign": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it WRITE: assign a team member (by name) to a lead. Reversible with workiz_unassign_lead. Workiz: POST /lead/assign/.
Annotations the server declares
- title: Assign a team member to a lead
- destructiveHint: true
workiz_convert_lead_to_jobWRITE (no API undo): convert a lead into a job.No findings
Why it is in this group
- The name "workiz_convert_lead_to_job" says "convert": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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/.
Annotations the server declares
- title: Convert a lead to a job
- destructiveHint: true
workiz_create_jobWRITE: create a new job (schedule, client contact and address, type, source, notes).No findings
Why it is in this group
- The name "workiz_create_job" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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/.
Annotations the server declares
- title: Create a job
- destructiveHint: true
workiz_create_leadWRITE: create a new lead (client contact and address, requested time, job type, source, notes).No findings
Why it is in this group
- The name "workiz_create_lead" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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/.
Annotations the server declares
- title: Create a lead
- destructiveHint: true
workiz_mark_lead_lostWRITE: mark a lead as lost.No findings
Why it is in this group
- The name "workiz_mark_lead_lost" says "mark": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it WRITE: mark a lead as lost. Reversible with workiz_activate_lead. Workiz: POST /lead/markLost/{UUID}/.
Annotations the server declares
- title: Mark a lead as lost
- destructiveHint: true
workiz_unassign_jobWRITE: remove a team member (by name) from a job.No findings
Why it is in this group
- The name "workiz_unassign_job" says "unassign": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it WRITE: remove a team member (by name) from a job. Reversible with workiz_assign_job. Workiz: POST /job/unassign/.
Annotations the server declares
- title: Unassign a team member from a job
- destructiveHint: true
workiz_unassign_leadWRITE: remove a team member (by name) from a lead.No findings
Why it is in this group
- The name "workiz_unassign_lead" says "unassign": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it WRITE: remove a team member (by name) from a lead. Reversible with workiz_assign_lead. Workiz: POST /lead/unassign/.
Annotations the server declares
- title: Unassign a team member from a lead
- destructiveHint: true
workiz_update_jobWRITE: update fields on an existing job — status/sub-status, reschedule (JobDateTime/JobEndDateTime), contact, address, type, source, notes, tags.No findings
Why it is in this group
- The name "workiz_update_job" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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/.
Annotations the server declares
- title: Update a job
- destructiveHint: true
workiz_update_leadWRITE: update fields on an existing lead — status, schedule, contact, address, type, source, notes, tags.No findings
Why it is in this group
- The name "workiz_update_lead" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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/.
Annotations the server declares
- title: Update a lead
- destructiveHint: true
Only reads 8Show 8 read-only tools
workiz_get_jobFetch one job by UUID: schedule, status, client contact and address, totals and amount due, notes, tags and assigned team.Reads private dataNo findings
Why it is in this group
- The name "workiz_get_job" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "fetch" and "contact": it reads contacts.
Description, as the server wrote it 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}/.
Annotations the server declares
- title: Get one job
- readOnlyHint: true
workiz_get_leadFetch one lead by UUID: schedule, status, client contact and address, source, notes and assigned team.Reads private dataNo findings
Why it is in this group
- The name "workiz_get_lead" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "fetch" and "contact": it reads contacts.
Description, as the server wrote it Fetch one lead by UUID: schedule, status, client contact and address, source, notes and assigned team. Workiz: GET /lead/get/{UUID}/.
Annotations the server declares
- title: Get one lead
- readOnlyHint: true
workiz_get_team_memberFetch one team member by user id: name, role, field-tech flag, email, service areas, skills and active status.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "workiz_get_team_member" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "fetch" and "email": it reads mail.
- untrusted-inputThe description's first sentence says "fetch" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Get one team member
- readOnlyHint: true
workiz_get_user_time_offList one team member's FUTURE time off, by their name.No findings
Why it is in this group
- The name "workiz_get_user_time_off" says "get": a word for reading.
Description, as the server wrote it List one team member's FUTURE time off, by their name. Workiz: GET /TimeOff/get/{USER_NAME}.
Annotations the server declares
- title: Get a team member's time off
- readOnlyHint: true
workiz_list_jobsList jobs, most recently scheduled first (sorted by JobDateTime, descending).No findings
Why it is in this group
- The name "workiz_list_jobs" says "list": a word for reading.
Description, as the server wrote it 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/.
Annotations the server declares
- title: List jobs
- readOnlyHint: true
workiz_list_leadsList leads, most recent first (sorted by LeadDateTime, descending).No findings
Why it is in this group
- The name "workiz_list_leads" says "list": a word for reading.
Description, as the server wrote it 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/.
Annotations the server declares
- title: List leads
- readOnlyHint: true
workiz_list_teamList the account's active team members: id, name, role, whether they are a field tech, email, service areas and skills.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "workiz_list_team" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "email": it reads mail.
- untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it 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/.
Annotations the server declares
- title: List team members
- readOnlyHint: true
workiz_list_time_offList FUTURE time off (start, end, userName — 'Entire Business' for company-wide closures).No findings
Why it is in this group
- The name "workiz_list_time_off" says "list": a word for reading.
Description, as the server wrote it 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/.
Annotations the server declares
- title: List upcoming time off
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data4
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:38 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 11 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://workiz.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://workiz.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 11 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://workiz.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://workiz.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.40.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http workiz https://workiz.usefulapi.io/mcpclaude mcp add --transport http workiz https://workiz.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__workiz__workiz_list_jobs",
"mcp__workiz__workiz_get_job",
"mcp__workiz__workiz_list_leads",
"mcp__workiz__workiz_get_lead",
"mcp__workiz__workiz_list_team",
"mcp__workiz__workiz_get_team_member",
"mcp__workiz__workiz_list_time_off",
"mcp__workiz__workiz_get_user_time_off"
],
"ask": [],
"deny": [
"mcp__workiz__workiz_create_job",
"mcp__workiz__workiz_update_job",
"mcp__workiz__workiz_assign_job",
"mcp__workiz__workiz_unassign_job",
"mcp__workiz__workiz_create_lead",
"mcp__workiz__workiz_update_lead",
"mcp__workiz__workiz_assign_lead",
"mcp__workiz__workiz_unassign_lead",
"mcp__workiz__workiz_convert_lead_to_job",
"mcp__workiz__workiz_mark_lead_lost",
"mcp__workiz__workiz_activate_lead"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as workiz. Review it before you use it.
Capability tags behind 4 rules
- mcp__workiz__workiz_get_job private-data
- mcp__workiz__workiz_get_lead private-data
- mcp__workiz__workiz_list_team private-data, untrusted-input
- mcp__workiz__workiz_get_team_member private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/workiz/verify?hash=34b3207495db93a7b953d147d0c2b24cc4e8e96ee1e3183a2f9303a9c6f1b18b" | jq -e '.changed == false'Pinned hash 34b3207495db, from Oct 25, 2026, 23:20 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/workiz/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/workiz)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:19 UTC.
Workiz MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Workiz MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 19 tools, 11 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Workiz MCP by usefulapi delete data?
- Yes. 11 tools can delete, cancel or revoke something: workiz_create_job, workiz_update_job, workiz_assign_job, workiz_unassign_job, workiz_create_lead, workiz_update_lead and 5 more.
Can the Workiz MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Workiz MCP by usefulapi have?
- 19 tools: 11 destructive, 8 read. workiz_create_job, workiz_update_job, workiz_assign_job, workiz_unassign_job, workiz_create_lead, workiz_update_lead, workiz_assign_lead, workiz_unassign_lead and 11 more.
Does the Workiz MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Workiz MCP by usefulapi send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Workiz MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.