devflow-mcp (vulq-cmd/jira-dev-mcp) is an MCP server listed on the M8ven Trust Index. It scores 46 out of 100, grade D. It declares 22 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
46/100

devflow-mcp

A read-only MCP server that securely serves Jira (Server/Data Center) data to Claude Code without exposing the personal access token, with optional GitLab integration.

→ vulq-cmd/jira-dev-mcp· 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

⚡ 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

vulq-cmd

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
⚠️
Tool descriptions don’t match what handlers do
1 tool describes read intent but its handler mutates — figma_get_frames (line 117: with open(p, "wb") as fh:)
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 3 credentials: GITLAB_TOKEN, NOTION_TOKEN, FIGMA_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes14 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

fn
figma_get_frames

Render frame Figma ra PNG (local path) để xem design bằng vision (read-only).

figma_get_specs

Trích SPEC CHÍNH XÁC từ Figma node tree: size px, màu hex, text, font (read-only).

figma_get_comments

Đọc COMMENT trên file Figma (read-only) — text + tác giả + node được pin.

gitlab_search_mrs

Find merge requests referencing a ticket key (read-only, heuristic).

gitlab_get_mr

Get a single merge request (read-only).

gitlab_get_mr_commits

List commits in a merge request (read-only).

gitlab_get_commits

List recent commits for a project branch/ref (read-only).

gitlab_get_commit_diff

Get a commit's diff (read-only). Truncated for token efficiency.

gitlab_get_pipeline_status

Get latest pipeline status for a branch/ref or a merge request (read-only).

gitlab_search_code

Search code (blobs) across GitLab (read-only). Degrades gracefully.

gitlab_get_file

Read a repo file's content (read-only). Truncated for token efficiency.

gitlab_create_mr

Create a merge request — OPT-IN write (GITLAB_ENABLE_WRITE=true), confirm-gated.

notion_get_page

Đọc nội dung 1 Notion page (text, read-only). Nhận URL hoặc page id.

// 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.
configDEVFLOW_TRANSPORT
configDEVFLOW_HTTP_HOST
configDEVFLOW_HTTP_PORT
configJIRA_ACTIVE_STATUSES
configJIRA_ASSIGNEES_FIELD
configJIRA_SPRINT_FIELD
configJIRA_BOARD_ID
configJIRA_VERIFY_SSLfalse only for trusted internal self-signed certs.
configJIRA_HTTP_TIMEOUT
configGITLAB_URL"": "${GITLAB_URL}",
🔐 secretGITLAB_TOKEN"": "${GITLAB_TOKEN}"
configGITLAB_VERIFY_SSL
configGITLAB_ENABLE_WRITE
configJIRA_ENABLE_WRITE
configJIRA_ALLOWED_TRANSITIONS
🔐 secretNOTION_TOKEN
configNOTION_VERSION
🔐 secretFIGMA_TOKEN
configFIGMA_HTTP_TIMEOUT
configDEVFLOW_HTTP_RETRIES
configDEVFLOW_HTTP_BACKOFF
configJIRA_EXTRA_FIELDS
configJIRA_DESC_MAX
// 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 — fn (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); figma_get_frames (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); figma_get_specs (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.

Descriptions match behaviour

1 tool describes read intent but its handler mutates — figma_get_frames (line 117: with open(p, "wb") as fh:)

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool handlers catch errors

Only 3/13 tool handlers wrap calls in try/catch (23%)

Wrap each tool handler body in try/catch and return a structured error response.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tests exist

No test files found

Add tests that exercise each declared tool.

Tool description accuracy

figma_get_frames: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

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/vulq-cmd/jira-dev-mcp?variant=verified)](https://m8ven.ai/mcp/vulq-cmd/jira-dev-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: ca88ba3fdb73f61e7ef1e2b06a3c88ed839a111e
code hash: 7b1a522058a6d491c6cd4697a2dd5bbd79867e7efec2a18656bd7cd1ea1ebdac
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