Redmine Pm MCP Server

redmine-pm-mcp npm v0.1.0

Published by drahmatdev — 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

high Sensitive-source and external-sink co-existMTC-FLOW-004

Tools that read sensitive data ([redmine_project_files_list]) and tools that can send data out ([redmine_upload_file]) are exposed together. An agent can move private data to the sink.

Evidence: sources [redmine_project_files_list] → sinks [redmine_upload_file]

Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.

Location: flow redmine_project_files_list → redmine_upload_file

Tools 64

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

  • redmine_project_files_listreads sensitive data
  • redmine_upload_filenetwork egress
  • redmine_attachment_deleteno sensitive capability
  • redmine_attachment_getno sensitive capability
  • redmine_custom_fields_listno sensitive capability
  • redmine_enumerations_listno sensitive capability
  • redmine_group_createno sensitive capability
  • redmine_group_deleteno sensitive capability
  • redmine_group_getno sensitive capability
  • redmine_group_updateno sensitive capability
Show 54 more tools ↓
  • redmine_group_user_addno sensitive capability
  • redmine_group_user_removeno sensitive capability
  • redmine_groups_listno sensitive capability
  • redmine_issue_categories_listno sensitive capability
  • redmine_issue_category_createno sensitive capability
  • redmine_issue_category_deleteno sensitive capability
  • redmine_issue_category_getno sensitive capability
  • redmine_issue_category_updateno sensitive capability
  • redmine_issue_createno sensitive capability
  • redmine_issue_deleteno sensitive capability
  • redmine_issue_getno sensitive capability
  • redmine_issue_journals_listno sensitive capability
  • redmine_issue_relation_createno sensitive capability
  • redmine_issue_relation_deleteno sensitive capability
  • redmine_issue_relations_listno sensitive capability
  • redmine_issue_statuses_listno sensitive capability
  • redmine_issue_updateno sensitive capability
  • redmine_issue_watcher_addno sensitive capability
  • redmine_issue_watcher_removeno sensitive capability
  • redmine_issues_listno sensitive capability
  • redmine_membership_createno sensitive capability
  • redmine_membership_deleteno sensitive capability
  • redmine_membership_updateno sensitive capability
  • redmine_memberships_listno sensitive capability
  • redmine_my_account_getno sensitive capability
  • redmine_news_listno sensitive capability
  • redmine_project_archiveno sensitive capability
  • redmine_project_createno sensitive capability
  • redmine_project_deleteno sensitive capability
  • redmine_project_getno sensitive capability
  • redmine_project_unarchiveno sensitive capability
  • redmine_project_updateno sensitive capability
  • redmine_projects_listno sensitive capability
  • redmine_queries_listno sensitive capability
  • redmine_role_getno sensitive capability
  • redmine_roles_listno sensitive capability
  • redmine_searchno sensitive capability
  • redmine_time_entries_listno sensitive capability
  • redmine_time_entry_createno sensitive capability
  • redmine_time_entry_deleteno sensitive capability
  • redmine_time_entry_getno sensitive capability
  • redmine_time_entry_updateno sensitive capability
  • redmine_trackers_listno sensitive capability
  • redmine_user_getno sensitive capability
  • redmine_users_listno sensitive capability
  • redmine_version_createno sensitive capability
  • redmine_version_deleteno sensitive capability
  • redmine_version_getno sensitive capability
  • redmine_version_updateno sensitive capability
  • redmine_versions_listno sensitive capability
  • redmine_wiki_page_deleteno sensitive capability
  • redmine_wiki_page_getno sensitive capability
  • redmine_wiki_page_updateno sensitive capability
  • redmine_wiki_pages_listno 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
v0.1.0 latest A 93/100 1 1.10.0 2026-07-25

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-pm-mcp/badge.svg)](https://mcptrustchecker.com/registry/redmine-pm-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/redmine-pm-mcp"><img src="https://mcptrustchecker.com/registry/redmine-pm-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/redmine-pm-mcp/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-pm-mcp --online

Use the free API → How scoring works

More in Developer Tools