Clockwork MCP Server
clockwork-mcp
npm
v0.4.1
Source verified
Published by fridzema — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
MCP server for Laravel Clockwork - debug Laravel apps with Claude Code
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.
Findings 1
high Shell/command execution in server code (dist/index.js)MTC-SRC-002
In the server's implementation (`dist/index.js:9`): 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: port { execSync } from "child_process"; function detectSqliteStorage(projectPath, options = {}) { try { const phpC
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/index.js
Tools 38
Each tool and what it can reach — statically extracted from the published source.
get_logsreads sensitive dataanalyze_exceptionsno sensitive capabilityanalyze_route_performanceno sensitive capabilityanalyze_slow_queriesno sensitive capabilitycompare_requestsno sensitive capabilitydetect_memory_issuesno sensitive capabilitydetect_n_plus_oneno sensitive capabilityexplain_request_flowno sensitive capabilityget_auth_userno sensitive capabilityget_cache_operationsno sensitive capability
Show 28 more tools ↓
get_cache_statsno sensitive capabilityget_call_graphno sensitive capabilityget_clockwork_statusno sensitive capabilityget_commandno sensitive capabilityget_eventsno sensitive capabilityget_http_requestsno sensitive capabilityget_latest_requestno sensitive capabilityget_log_stack_traceno sensitive capabilityget_middleware_chainno sensitive capabilityget_performance_summaryno sensitive capabilityget_queriesno sensitive capabilityget_query_stack_traceno sensitive capabilityget_query_statsno sensitive capabilityget_queue_jobno sensitive capabilityget_redis_commandsno sensitive capabilityget_requestno sensitive capabilityget_route_detailsno sensitive capabilityget_session_datano sensitive capabilityget_testno sensitive capabilityget_timelineno sensitive capabilityget_viewsno sensitive capabilityget_xdebug_hotspotsno sensitive capabilityget_xdebug_profileno sensitive capabilitylist_commandsno sensitive capabilitylist_queue_jobsno sensitive capabilitylist_requestsno sensitive capabilitylist_testsno sensitive capabilitysearch_requestsno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (38 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.4.1 latest |
A 94/100 | 1 | 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 clockwork-mcp --onlineMore in Databases
Security scan results for the A5sql MCP server.
Expose AgentsKit tools as an MCP server — use them from Claude Desktop, Cursor, Windsurf, or any MCP host.
MCP server for Aiven cloud data platform - manage PostgreSQL, Kafka, and other services
MCP Server for All-Inkl.com hosting via KAS API
Structured aquarium, marine, terrarium and paludarium data for AI agents.
MCP server that gives your AI agent real vehicle data — specs, representative images, federal recalls, owner complaints, service bulletins, defect investigations, and OBD-II DTC reference — from the CarVector API.