Robin Saige we check the tools AI agents call

DeskMonitor

com.thedeskmonitor/mcp

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

— the operator's own registry description reported

Publisher com.thedeskmonitor · first seen 2026-08-12 · endpoint https://api.thedeskmonitor.com/api/mcp/v1

allow
verdict
mid-solo
cluster
ok_tools
answers
24
tools served

Dependency rating derived

allow
allow — alive & usable · retrieval-public ● · V1 shows its work ◐
allow — because answers ●, 24 tools legible (band A) ●, no confirmed drift in 2 probes ●; not yet checked: truth (0 runs)

Cluster mid-solo · distinctiveness 0.512 (moderate). Every figure is a percentile or class within the 11,094-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersalive_tools
latency356 ms
vs populationtypical
protocolcurrent
authopen
Can it be used? Q4 · observed
tools24
vs populationmid
capabilities3
harnessA
Did it hold when checked? Q3–Q4 · derived
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_a8ed9f16c079bf8d65fb0531 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Q1Does it answer?alive & usable — 2 probes ●evidence ↓
Q2What is it?retrieval-public ● evidence ↓
Q3Can it be checked?V1 shows its work ◐evidence ↓
Q4Did it hold?harness A · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?mid-solo · 1 on its host (context, not verdict) ◐evidence ↓

● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)
datetypewhat changed
2026-08-12outcomefirst probe: ok_tools

What kind of tools these are derived

Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. Classification evidence: classified from tool names/descriptions/annotations WE OBSERVED. What checking applies to each kind (the full methodology →):

naturetoolsmeaning what checking applies
retrieval-public16serves public factstruth-checkable against a public source — the V-ladder applies in full
action3changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
generative3creates contentno answer key exists; disclosure + stability checks, never truth verdicts
retrieval-private2serves the caller's own dataoutside truth-checking is impossible BY NATURE, not by failure — the operator-invited pathway applies

Tools last seen observed

ask_workforce clock_in clock_out get_analytics_feature_usage get_analytics_overview get_analytics_questions get_capabilities get_dashboard_summary get_data_dictionary get_demo_scenarios get_employee_details get_pricing_and_plans get_productivity_overview get_started_guide get_workload_alerts invite_staff list_employees list_my_timesheet list_pending_approvals list_recent_activity start_free_trial summarize_team_hours switch_to_demo switch_to_production

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility checktools passingok
name is clear & specific24/24
has a description24/24
description is substantive24/24
parameters are typed24/24
parameters are described21/2421/24

24 of 24 tools graded · 24 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18
protocol version
session model
1.6.0
server version DeskMonitor MCP Server

Capabilities: prompts resources tools

Drift observed

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T19:58:34Zok_tools2003562025-06-18
2026-08-12T05:33:48Zok_tools2004132025-06-18

Watch or embed this verdict

verdict badge

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/com.thedeskmonitor/mcp.svg)](https://robinsaige.com/s/com.thedeskmonitor/mcp)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview