Home / MCP registry index / de.workloadzero/mcp

workload.zero

de.workloadzero/mcp in the official MCP registry. Endpoint https://mcp.workloadzero.de/mcp. Source: github.com/getitdone-gmbh/workload-zero-mcp.

The registry describes it as: Back office, projects, hiring and CRM in one suite. Claude's work stays a draft until you approve.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http workloadzero https://mcp.workloadzero.de/mcp

{
  "mcpServers": {
    "workloadzero": {
      "url": "https://mcp.workloadzero.de/mcp"
    }
  }
}

code --add-mcp '{"name":"workloadzero","type":"http","url":"https://mcp.workloadzero.de/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

get_my_profile update_my_profile list_users get_my_colleagues list_team_members search list_notifications mark_notifications_read get_activity_feed list_projects get_project create_project update_project delete_project get_project_budget list_project_members add_project_member update_project_member remove_project_member list_clients create_client list_tasks get_task create_task update_task assign_task_to_me unassign_me_from_task list_subtasks move_task_on_board add_task_link remove_task_link set_task_work_links delete_task restore_task list_deleted_tasks get_task_history list_task_tags add_task_comment update_task_comment delete_task_comment toggle_task_comment_reaction attach_file_to_task remove_task_attachment get_my_time_entries list_time_entries log_time update_time_entry delete_time_entry start_timer stop_timer get_active_timer discard_timer get_todays_goals get_week_goals list_goals get_goals_for_task create_goal update_goal complete_goal check_goal_item and 89 more

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-04): 7267f98f4e3b1d05. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/de-workloadzero-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/de-workloadzero-mcp)

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. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

CRM MCP servers