Devpipe MCP Server
devpipe-mcp
npm
v0.2.7
Source verified
Published by drewkhoury — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
Model Context Protocol server for devpipe - helps AI assistants interact with devpipe to manage development workflows
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 2
high Shell/command execution in server code (dist/utils.js)MTC-SRC-002
In the server's implementation (`dist/utils.js:4`): 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 { exec } from 'child_process'; import { promisify } from 'util'; import { readFile, access, readdir, stat } fro
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/utils.js
high Shell/command execution in server code (src/utils.ts)MTC-SRC-002
In the server's implementation (`src/utils.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: import { exec } from 'child_process'; import { promisify } from 'util'; import { readFile, access, readdir, stat } fro
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 src/utils.ts
Tools 55
Each tool and what it can reach — statically extracted from the published source.
Changed files listreads sensitive dataview_run_logsreads sensitive dataAggregated metrics summaryno sensitive capabilityAll devpipe releasesno sensitive capabilityanalyze_projectno sensitive capabilityanalyze-configno sensitive capabilityAvailable devpipe commandsno sensitive capabilityChange correlation analysisno sensitive capabilitycheck_devpipeno sensitive capabilityCLI reference documentationno sensitive capability
Show 45 more tools ↓
compare_runsno sensitive capabilityConfig validation documentationno sensitive capabilityConfiguration documentationno sensitive capabilityConfiguration schemano sensitive capabilityconfigure-metricsno sensitive capabilitycreate_configno sensitive capabilitycreate-taskno sensitive capabilityCurrent devpipe configurationno sensitive capabilityDashboard HTML templateno sensitive capabilitydebug-failureno sensitive capabilitydevpipe READMEno sensitive capabilityExample configurationno sensitive capabilityFeatures documentationno sensitive capabilityFlaky task detectionno sensitive capabilitygenerate_ci_configno sensitive capabilitygenerate_taskno sensitive capabilityget_dashboard_datano sensitive capabilityget_last_runno sensitive capabilityget_pipeline_healthno sensitive capabilityGit repository statusno sensitive capabilityIDE HTML templateno sensitive capabilityInstalled devpipe versionno sensitive capabilityLast run resultsno sensitive capabilityLatest devpipe releaseno sensitive capabilitylist_tasksno sensitive capabilitylist_tasks_verboseno sensitive capabilitymcp-infono sensitive capabilityoptimize-pipelineno sensitive capabilityparse_metricsno sensitive capabilityPerformance regression detectionno sensitive capabilityPipeline summaryno sensitive capabilitypredict_impactno sensitive capabilityProject root documentationno sensitive capabilityRecent task failuresno sensitive capabilityrun_pipelineno sensitive capabilitySafety checks documentationno sensitive capabilitysecurity-reviewno sensitive capabilityTask definitionsno sensitive capabilityTask execution historyno sensitive capabilitytaskIdno sensitive capabilitytaskTypeno sensitive capabilitytechnologyno sensitive capabilitytoolno sensitive capabilityvalidate_configno sensitive capabilityWatchPaths analysisno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (55 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.2.7 latest |
A 94/100 | 2 | 1.13.0 | 2026-09-09 |
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 devpipe-mcp --onlineMore in Developer Tools
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.