temporal-mcp
npm
v0.2.1
Source verified
Published by stevekinney — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
Read-only MCP server for inspecting Temporal workflows, schedules, infrastructure, and documentation.
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 − 6 = 94. 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 |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
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.
In the server's implementation (`dist/cli.js:594`): 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: spawnSync } from "node:child_process"; function getCorpusPath(homeDirectory = homedir2()) { return join2(homeDirector
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 dist/cli.js
Each tool and what it can reach — statically extracted from the published source.
docs.getno sensitive capabilitydocs.refreshno sensitive capabilitydocs.searchno sensitive capabilitydocs.statusno sensitive capabilitytemporal.cluster.infono sensitive capabilitytemporal.connection.checkno sensitive capabilitytemporal.namespace.describeno sensitive capabilitytemporal.namespace.listno sensitive capabilitytemporal.schedule.describeno sensitive capabilitytemporal.schedule.listno sensitive capabilitytemporal.schedule.matching-timesno sensitive capabilitytemporal.search-attributes.listno sensitive capabilitytemporal.task-queue.configurationno sensitive capabilitytemporal.task-queue.describeno sensitive capabilitytemporal.worker.deployment.describeno sensitive capabilitytemporal.worker.deployment.listno sensitive capabilitytemporal.worker.deployment.reachabilityno sensitive capabilitytemporal.worker.deployment.version.describeno sensitive capabilitytemporal.worker.task-reachabilityno sensitive capabilitytemporal.worker.versioning-rulesno sensitive capabilitytemporal.workflow.countno sensitive capabilitytemporal.workflow.describeno sensitive capabilitytemporal.workflow.historyno sensitive capabilitytemporal.workflow.history.reverseno sensitive capabilitytemporal.workflow.history.summarizeno sensitive capabilitytemporal.workflow.listno sensitive capabilitytemporal.workflow.queryno sensitive capabilitytemporal.workflow.resultno sensitive capabilityScan 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.2.1 latest |
A 94/100 | 1 | 1.13.0 | 2026-09-07 |
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.
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 temporal-mcp --online
Independent packages implementing the same tool, scanned with the same engine. Compare all 6 side by side →
MCP server for time, timezone, and duration tools. Runs locally over stdio and on Cloudflare Workers.
MCP server for the Temporal HTTP API — manage workflows, namespaces, and schedules from any MCP-compatible IDE
MCP server providing temporal intelligence for AI: 69 tools for timezone conversions, 32 cultural calendars, 247+ country holidays, 5 financial markets, business time calculations, astronomical events, prayer times, astrology, duration/period calculations
Temporal grounding for LLM agents: per-thread elapsed time, day rollover, and resume detection as an MCP server.
MCP server for Temporal workflow orchestration
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.