Redmine Mcp Workflows MCP Server

redmine-mcp-workflows PyPI v1.0.0

Published by avicennasis — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

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 − 7 = 93. 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:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

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

critical Completed toxic-flow trifecta across toolsMTC-FLOW-002

This server (without client built-ins) exposes a complete data-exfiltration chain: redmine_download_attachment → redmine_list_project_files → redmine_bulk_create_issues. Untrusted input is ingested, private data is read, and it can be sent to an external sink via the agent composing the tools (→). Static analysis proves the primitive exists, not that a specific run will occur.

Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.

Location: flow redmine_download_attachment → redmine_list_project_files → redmine_bulk_create_issues

Tools 81

Each tool and what it can reach — statically extracted from the published source.

  • redmine_bulk_create_issuesnetwork egress
  • redmine_create_issuenetwork egress
  • redmine_create_issue_categorynetwork egress
  • redmine_download_attachmentingests untrusted input
  • redmine_get_groupingests untrusted input
  • redmine_get_issueingests untrusted input
  • redmine_get_roleingests untrusted input
  • redmine_get_useringests untrusted input
  • redmine_get_versioningests untrusted input
  • redmine_get_wiki_pageingests untrusted input
Show 71 more tools ↓
  • redmine_invalidate_cachenetwork egress
  • redmine_list_project_filesreads sensitive data
  • redmine_add_commentno sensitive capability
  • redmine_add_group_userno sensitive capability
  • redmine_add_membershipno sensitive capability
  • redmine_add_relationno sensitive capability
  • redmine_add_watcherno sensitive capability
  • redmine_archive_projectno sensitive capability
  • redmine_assign_issue_to_versionno sensitive capability
  • redmine_bulk_closeno sensitive capability
  • redmine_bulk_update_issuesno sensitive capability
  • redmine_close_issueno sensitive capability
  • redmine_create_groupno sensitive capability
  • redmine_create_messageno sensitive capability
  • redmine_create_newsno sensitive capability
  • redmine_create_projectno sensitive capability
  • redmine_create_time_entryno sensitive capability
  • redmine_create_versionno sensitive capability
  • redmine_create_wiki_pageno sensitive capability
  • redmine_delete_groupno sensitive capability
  • redmine_delete_issueno sensitive capability
  • redmine_delete_issue_categoryno sensitive capability
  • redmine_delete_messageno sensitive capability
  • redmine_delete_newsno sensitive capability
  • redmine_delete_projectno sensitive capability
  • redmine_delete_time_entryno sensitive capability
  • redmine_delete_versionno sensitive capability
  • redmine_delete_wiki_pageno sensitive capability
  • redmine_describe_projectno sensitive capability
  • redmine_describe_trackerno sensitive capability
  • redmine_get_journalsno sensitive capability
  • redmine_list_boardsno sensitive capability
  • redmine_list_custom_fieldsno sensitive capability
  • redmine_list_enumerationsno sensitive capability
  • redmine_list_groupsno sensitive capability
  • redmine_list_issue_categoriesno sensitive capability
  • redmine_list_issue_statusesno sensitive capability
  • redmine_list_membershipsno sensitive capability
  • redmine_list_messagesno sensitive capability
  • redmine_list_newsno sensitive capability
  • redmine_list_projectsno sensitive capability
  • redmine_list_queriesno sensitive capability
  • redmine_list_relationsno sensitive capability
  • redmine_list_rolesno sensitive capability
  • redmine_list_time_entriesno sensitive capability
  • redmine_list_trackersno sensitive capability
  • redmine_list_usersno sensitive capability
  • redmine_list_versionsno sensitive capability
  • redmine_list_watchersno sensitive capability
  • redmine_remove_group_userno sensitive capability
  • redmine_remove_membershipno sensitive capability
  • redmine_remove_relationno sensitive capability
  • redmine_remove_watcherno sensitive capability
  • redmine_reply_messageno sensitive capability
  • redmine_requestno sensitive capability
  • redmine_searchno sensitive capability
  • redmine_search_issuesno sensitive capability
  • redmine_set_parent_issueno sensitive capability
  • redmine_unarchive_projectno sensitive capability
  • redmine_update_groupno sensitive capability
  • redmine_update_issueno sensitive capability
  • redmine_update_issue_categoryno sensitive capability
  • redmine_update_journalno sensitive capability
  • redmine_update_membershipno sensitive capability
  • redmine_update_newsno sensitive capability
  • redmine_update_projectno sensitive capability
  • redmine_update_time_entryno sensitive capability
  • redmine_update_versionno sensitive capability
  • redmine_update_wiki_pageno sensitive capability
  • redmine_upload_attachmentno sensitive capability
  • redmine_upload_project_fileno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

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.

VersionScoreFindingsEngineScanned
v1.0.0 latest A 93/100 1 1.9.0 2026-07-23

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.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/redmine-mcp-workflows/badge.svg)](https://mcptrustchecker.com/registry/redmine-mcp-workflows)
HTML
<a href="https://mcptrustchecker.com/registry/redmine-mcp-workflows"><img src="https://mcptrustchecker.com/registry/redmine-mcp-workflows/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/redmine-mcp-workflows/badge.json via https://img.shields.io/endpoint?url=…

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 redmine-mcp-workflows --online --registry pypi

Use the free API → How scoring works

More in Developer Tools