Redmine MCP Server

jztan/redmine-mcp-server

MCP server connecting AI assistants to Redmine: issues, projects, wikis, time tracking, agile boards, and CRM, with OAuth2 multi-user support

MCP Servers Python Listed MIT

Is Redmine MCP Server safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.6 / 10

Provenance None

Signed commits 37%

Last push today

Compare Redmine MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Redmine MCP Server scores 66.0/100 (Grade B), ranked #441 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.6/10; 37% of recent commits are signed; last pushed 2026-09-26. Every point is earned from checkable signals — never paid placement. How scoring works →

How Redmine MCP Server compares in MCP Servers

Bars show each HVTrust score; the tick marks Redmine MCP Server’s 66.0.

Where the 66.0 comes from

HVTrust dimensions vs the MCP Servers average

66.0 / 100 · 100.0% confidence

Redmine MCP Server MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

8.8 / 25

1.5 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

13.3 / 17

1.1 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

7.9 above avg 12.1

AdoptionLog-scaled stars · package downloads

8.1 / 20

0.9 above avg 7.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 225 spots (#671 → #446)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.6/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for Redmine MCP Server View MCP Servers Report missing data

68.6

Activity sub-score · out of 100

#260

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-26

today

Commits (4 wk)

207

Downloads (7d)

421

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▲2

was #443

Analysis

Activity Inputs

68.6 / 100

StarsRepository reach

11.4 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

7.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.6 / 10

OpenSSF Scorecard · scanned Sep 14, 2026

Signed Commits

37%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 2

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 6

SAST 0

Security-Policy 4

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 8

Common questions about Redmine MCP Server

Redmine MCP Server has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Redmine MCP Server publish package provenance?

No published build provenance is currently detected for Redmine MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Redmine MCP Server have an OpenSSF Scorecard?

Redmine MCP Server has an OpenSSF Scorecard score of 5.6/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Redmine MCP Server actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Redmine MCP Server use?

Redmine MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Redmine MCP Server's commits signed?

37% of the last 100 commits to Redmine MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

Redmine MCP Server appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to Redmine MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Redmine MCP Server?

For maintainers

HVTrust scores Redmine MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 225 spots (#671 → #446)

2026-09-23

HVTrust Changed

HVTrust up 34.2pts (31.5 → 65.7)

2026-09-22

Newly Listed

First tracked at rank #671

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank dropped 12 spots (#440 → #452)

2026-09-13

Rank Moved

Rank dropped 11 spots (#412 → #423)

2026-09-11

Rank Moved

Rank dropped 10 spots (#403 → #413)

2026-09-10

Rank Moved

Rank dropped 16 spots (#387 → #403)

2026-09-09

Rank Moved

Rank dropped 10 spots (#377 → #387)

2026-09-07

Rank Moved

Rank dropped 21 spots (#353 → #374)

2026-09-05

Rank Moved

Rank dropped 40 spots (#305 → #345)

2026-09-03

Rank Moved

Rank dropped 18 spots (#280 → #298)

2026-08-31

Rank Moved

Rank dropped 26 spots (#257 → #283)

2026-08-28

Scorecard Added

OSSF Scorecard: 5.6/10

2026-08-28

Grade Changed

Trust grade D → B

2026-08-28

Rank Moved

Rank rose 550 spots (#802 → #252)

2026-08-28

HVTrust Changed

HVTrust up 27.9pts (37.5 → 65.4)

2026-08-27

Rank Moved

Rank dropped 22 spots (#780 → #802)

2026-08-26

Rank Moved

Rank dropped 101 spots (#679 → #780)

2026-08-16

Rank Moved

Rank dropped 16 spots (#662 → #678)

2026-08-10

Rank Moved

Rank dropped 29 spots (#634 → #663)

2026-08-08

Newly Listed

First tracked at rank #634

GitHub → PyPI: redmine-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/redmine-mcp-server.svg)](https://hvtracker.net/agents/redmine-mcp-server)
            
HTML:
            <a href="https://hvtracker.net/agents/redmine-mcp-server"><img src="https://hvtracker.net/badge/redmine-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON