Home / MCP registry index / io.usefulapi/workiz
Workiz MCP by usefulapi
io.usefulapi/workiz in the official MCP registry.
Endpoint https://workiz.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Manage Workiz jobs and leads: create, update, assign team members and convert leads to jobs.
We read its 19 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
workiz_list_jobs workiz_get_job workiz_list_leads workiz_get_lead workiz_list_team workiz_get_team_member workiz_list_time_off workiz_get_user_time_off workiz_create_job workiz_update_job workiz_assign_job workiz_unassign_job workiz_create_lead workiz_update_lead workiz_assign_lead workiz_unassign_lead workiz_convert_lead_to_job workiz_mark_lead_lost workiz_activate_lead
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-workiz)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.