DeskMonitor

warnings

api.thedeskmonitor.com

DeskMonitor: 24 workforce-intelligence MCP tools, OAuth 2.1, free demo key included.

https://api.thedeskmonitor.com/api/mcp/v1WebsiteOAuthMCP 2025-06-18v1.6.0last checked 24 Aug 2026spoke MCP on 3 of 3 checks (30 days)initialize in 427 ms

How to authenticate

Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	OAuth
Issuer	https://api.thedeskmonitor.com
Dynamic client registration	✓Advertised (RFC 7591)
Client ID Metadata Document	✕Not advertised
PKCE	✓S256
Grant types	authorization_code, refresh_token
Scopes	mcp:read, mcp:write
Protected-resource metadata	✓Published (RFC 9728)
Anonymous access	Handshake succeeds; 24 tools listable
Credentials demanded in prose	✕clock_in, clock_out, get_capabilities, start_free_trial, get_analytics_overview, get_analytics_feature_usage These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error.
Documentation	https://thedeskmonitor.com/ai-commands

What the probe found

warningTools needing credentials are listed without a challenge

6 of the 24 tools listed anonymously say in their own descriptions that they need an account or a key (clock_in, clock_out, get_capabilities, start_free_trial, get_analytics_overview, get_analytics_feature_usage), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

24 tools usable without signing in

The server exposes a public surface before authorization: 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.

Tools

get_started_guideget_data_dictionaryswitch_to_demoswitch_to_productionget_demo_scenariosget_dashboard_summarylist_employeesget_employee_detailslist_my_timesheetsummarize_team_hourslist_pending_approvalslist_recent_activityget_workload_alertsget_productivity_overviewclock_inclock_outinvite_staffget_capabilitiesget_pricing_and_plansstart_free_trialask_workforceget_analytics_questionsget_analytics_overviewget_analytics_feature_usage

Contract history

No contract recorded yet — the server has not answered an anonymous connection.

Run this server? A verified owner can publish snapshots with their own credentials, and the contract history starts here, marked owner-reported.

mcpi-cli publish https://api.thedeskmonitor.com/api/mcp/v1

Get alerted when this contract changes

Depend on this server? Leave an email. No contract is on record here yet, so alerts can only start once one is published — and alerts are being built; signing up is what tells us to hurry.

Prefer a feed reader? This page's contract changes are also an Atom feed.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/deskmonitor/badge.svg)](https://mcpi.app/servers/deskmonitor)