Development Workflow MCP Server (programinglive/dev-workflow-mcp-server) is an MCP server listed on the M8ven Trust Index. It scores 50 out of 100, grade D. It declares 22 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
50/100

Development Workflow MCP Server

An MCP server that enforces development discipline and workflow best practices, guiding users through a structured process of coding, testing, documenting, committing, and releasing.

→ programinglive/dev-workflow-mcp-server· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

programinglive

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Known vulnerabilities in dependencies: 8 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 3 credentials: ADMIN_PASSWORD, JWT_SECRET, SESSION_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies8 high3 medium4 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.0.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

highvite@7.1.12GHSA-fx2h-pf6j-xcff

vite: `server.fs.deny` bypass on Windows alternate paths

highvite@7.1.12GHSA-p9ff-h696-f583

Vite Vulnerable to Arbitrary File Read via Vite Dev Server WebSocket

highvite@7.1.12GHSA-v2wj-q39q-566r

Vite: `server.fs.deny` bypassed with queries

highws@8.16.0GHSA-3h5v-q93c-6h6q

ws affected by a DoS when handling a request with many HTTP headers

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configADMIN_EMAIL
🔐 secretADMIN_PASSWORD
configADMIN_USERNAME
configAPI_PORT
configDEV_WORKFLOW_DB_PATHOverride path for the SQLite database file <project>/.state/dev-workflow.db
configDEV_WORKFLOW_DB_TYPE"": "postgres",
configDEV_WORKFLOW_DB_URL"": "postgres://USER:PASS@HOST:5432/devworkflow"
configDEV_WORKFLOW_FORCE_RELEASE
configDEV_WORKFLOW_SKIP_RELEASE
configDEV_WORKFLOW_STATE_FILE4. Define environment variables – In the Node.js panel add any environment variables you need (for example DEV_WORKFLOW_USER_ID or ). This keeps state files outside the web root if desired.
configDEV_WORKFLOW_USER_ID4. Define environment variables – In the Node.js panel add any environment variables you need (for example or DEV_WORKFLOW_STATE_FILE). This keeps state files outside the web root if desired.
configINIT_CWD
🔐 secretJWT_SECRET
🔐 secretSESSION_SECRET
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

22/22 tools missing one or more hints — start_task (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); mark_bug_fixed (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); create_feature_flow (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +19 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

13/22 tools referenced in tests (59%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

19 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

No arbitrary install scripts

Has postinstall/preinstall script — runs arbitrary code on npm install

Remove postinstall/preinstall hooks unless they’re essential.

Production dependencies are patched

0 critical, 6 high severity in production deps — @modelcontextprotocol/sdk@1.0.0 (high), vite@7.1.12 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

2 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 7 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/programinglive/dev-workflow-mcp-server?variant=verified)](https://m8ven.ai/mcp/programinglive/dev-workflow-mcp-server)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 83c9ba06fce6acd01c3ee3bd95c26e3f8b42930f
code hash: acfdafa08ee0d569830a4fb20cea4841a5a0f44730c8e29a5897b222d45a83c9
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client