Workflows (agentdesk) MCP Server
@agentdesk/workflows-mcp
npm
v0.1.8
Published by @agentdesk — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
MCP workflow orchestration tool with presets for thinking, coding and more
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 2 = 98. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 2
low Shell/command execution in packaging/dev tooling (__tests__/advanced-parameters-integration.test.ts)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`__tests__/advanced-parameters-integration.test.ts:5`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: dProcess, spawn } from "child_process"; import path from "path"; import { fileURLToPath } from "url"; import { McpTestCl
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server __tests__/advanced-parameters-integration.test.ts
low Shell/command execution in packaging/dev tooling (__tests__/tool-integration.test.ts)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`__tests__/tool-integration.test.ts:10`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: import { spawn } from "child_process"; // Create dirname equivalent for ES modules const __filename = fileURLToPath(im
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server __tests__/tool-integration.test.ts
Tools 1
Each tool and what it can reach — statically extracted from the published source.
placeholderno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (1 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.1.8 latest |
A 98/100 | 2 | 1.13.0 | 2026-09-07 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @agentdesk/workflows-mcp --onlineOther implementations of Workflows 6
Independent packages implementing the same tool, scanned with the same engine. Compare all 7 side by side →
Transcend MCP Server — Workflows tools.
Store, query, and create YAML workflow playbooks for LLM agents via MCP. STDIO or Streamable HTTP.
A Model Context Protocol (MCP) implementation for workflow management and automation.
An MCP (Model Context Protocol) server that enables AI agents to discover, create, and execute complex, multi-step workflows defined in simple YAML files. Allow your AI agents to better organize their tool usage and provide a more structured way to handle
Official EZTexting MCP server: SMS/MMS messaging, contacts, workflows, and account administration.
MCP server for DAG-based workflow execution with YAML definitions and LLM collaboration
More in Productivity & Workflow
MCP AgentChat - 让 AI Agent 通过 Telegram 与用户实时交互：发送消息、图片，等待用户回复
A Model Context Protocol (MCP) server for Airthings Air Quality Monitor devices.
MCP server for Anki
TypeScript package for reading and searching Apple Notes on macOS via direct SQLite access. Includes markdown conversion, attachment support, and offers a local MCP server!
Verified biotech catalyst calendar (PDUFA/AdComm/trial readouts) anchored to official sources.
Appointment booking platform letting agents check provider availability and create bookings.