Home / MCP registry index / com.thedeskmonitor/mcp
DeskMonitor
com.thedeskmonitor/mcp in the official MCP registry.
Endpoint https://api.thedeskmonitor.com/api/mcp/v1.
The registry describes it as: DeskMonitor: 24 workforce-intelligence MCP tools, OAuth 2.1, free demo key included.
We read its 24 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules.
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
get_started_guide get_data_dictionary switch_to_demo switch_to_production get_demo_scenarios get_dashboard_summary list_employees get_employee_details list_my_timesheet summarize_team_hours list_pending_approvals list_recent_activity get_workload_alerts get_productivity_overview clock_in clock_out invite_staff get_capabilities get_pricing_and_plans start_free_trial ask_workforce get_analytics_questions get_analytics_overview get_analytics_feature_usage
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-thedeskmonitor-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. 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.