npm:@cocaxcode/devflow-mcp

Item: npm:@cocaxcode/devflow-mcp
Rating: 85
Author: wmcp.sh

https://www.npmjs.com/package/@cocaxcode/devflow-mcp

85/100 · MCP Trust Grade · checked 3h ago · MCP 0.1.15

What it offers — 30 tools · Developer Tools

df_project_setup

Configurar un nuevo proyecto: vincula Jira + Git provider. Auto-detecta tipo de Jira, version API, provider Git y rama base. IMPORTANTE: Pide al usuar

df_project_update

Modificar la configuracion de un proyecto existente.

df_project_list

Listar todos los proyectos configurados.

df_project_switch

Cambiar el proyecto activo (de sesion). Al reiniciar vuelve al default por scope.

df_project_delete

Eliminar un proyecto configurado.

df_issues

Listar mis issues asignados en Jira. Soporta filtros opcionales por proyecto y estado.

df_issue

Obtener el detalle completo de un issue de Jira. Solo lectura, sin efectos secundarios.

df_statuses

Listar las transiciones disponibles para un issue (los estados a los que se puede mover desde su estado actual).

df_transition

Mover un issue a un nuevo estado. Requiere confirm: true para ejecutar. Sin confirm devuelve preview.

df_assign

Asignar un issue al usuario actual. Si el issue ya tiene asignado, no hace nada.

df_comment

A\xF1adir un comentario a un issue de Jira. Requiere confirm: true para ejecutar.

df_branch

Crear una nueva branch desde la rama base con formato feat/PROJ-123-desc o fix/PROJ-123-desc. Requiere confirm: true. Verifica que no haya cambios sin

df_find_branch

Buscar si existe una rama local o remota que contenga un issue key (ej: PROJ-123). Devuelve la rama si existe o null.

df_checkout

Cambiar a una rama existente. Verifica que no haya cambios sin pushear antes.

df_pull

Hacer pull de la rama actual desde el remote.

df_merge

Mergear una rama en la rama actual. Requiere confirm: true. Si hay conflictos, los reporta sin abortar.

df_push

Hacer push de la rama actual al remote. Requiere confirm: true para ejecutar. Sin confirm devuelve preview.

df_pr

Crear un Pull Request (GitHub) o Merge Request (GitLab) para la rama actual.

+12 more tools

Spec / packaging20%100

✓ depends on an MCP SDK
✓ declares a bin entry (runnable server)
✓ 30 tool(s) detected in source

Security (OWASP MCP)30%70

uses eval/exec/child_process (review for unsanitized input)
scanned 3 source files

Maintenance / popularity20%100

published within 90 days
16 published versions

Tool hygiene15%70

no TypeScript types
3 runtime deps

Transparency / provenance15%90

✓ public repository linked
✓ MIT license
32 weekly downloads

Findings

INFO Static analysis of npm package @cocaxcode/devflow-mcp@0.1.15 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.

Grade another server

We re-grade npm:@cocaxcode/devflow-mcp on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:@cocaxcode/devflow-mcp grade B

Share on X Open card image

https://wmcp.sh/mcp/grade/npm%3A%40cocaxcode%2Fdevflow-mcp

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade B](https://wmcp.sh/mcp/grade/npm%3A%40cocaxcode%2Fdevflow-mcp/badge.svg)](https://wmcp.sh/mcp/grade/npm%3A%40cocaxcode%2Fdevflow-mcp)

HTML

<a href="https://wmcp.sh/mcp/grade/npm%3A%40cocaxcode%2Fdevflow-mcp"><img src="https://wmcp.sh/mcp/grade/npm%3A%40cocaxcode%2Fdevflow-mcp/badge.svg" alt="MCP Trust Grade B · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.