Home / MCP registry index / io.usefulapi/deputy
Deputy MCP by usefulapi
io.usefulapi/deputy in the official MCP registry.
Endpoint https://deputy.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: See rosters, timesheets, leave and staff in Deputy, and create shifts, leave and memos.
We read its 21 tools on 2026-10-26. 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
deputy_whoami deputy_list_locations deputy_list_areas deputy_list_employees deputy_get_employee deputy_list_shifts deputy_get_shift deputy_list_timesheets deputy_get_timesheet deputy_list_leave deputy_get_employee_unavailability deputy_query_resource deputy_describe_resource deputy_create_shift deputy_update_shift deputy_publish_shifts deputy_create_leave_request deputy_add_unavailability deputy_create_memo deputy_update_timesheet deputy_approve_timesheet
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-deputy)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.