updated 2026-11-10 04:07 UTC

Redmine MCP Server

Repository Website by jztan

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 4.9 / 10
Provenance None
Signed commits 52%
Last push yesterday
Advisories None known
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 65.4/100 (Grade B), ranked #519 of 1374 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 4.9/10; 52% of recent commits are signed; no published advisory affects its latest release (redmine-mcp-server); last pushed 2026-11-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Redmine MCP Server could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Redmine MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/jztan/redmine-mcp-server, MIT, last pushed 2026-11-09. 52% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.9/10 (scanned Nov 1, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies6
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    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 0

  3. Published packages Linked, not attested

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: redmine-mcp-server 2.21.0. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-08-28 OSSF Scorecard: 5.6/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Redmine MCP Server’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Redmine MCP Server compares in MCP Servers

  1. #297 Laravel Boost 65.4 ±0
  2. #298 Umbraco CMS MCP Dev 65.4 ±0
  3. #299 Redmine MCP Server 65.4 this agent
  4. #300 Podman MCP Server 65.3 −0.1
  5. #301 Home Assistant MCP 65.3 −0.1

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

Where the 65.4 comes from

HVTrust dimensions vs the MCP Servers average

65.4 / 100 · 100.0% confidence

Redmine MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.7 / 25
2.1 below avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
12.7 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
19.8 / 20
7.6 above avg 12.2
AdoptionLog-scaled stars · package downloads
8.4 / 20
0.8 above avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-07
Grade Changed
Trust grade C → B
2026-11-07
Rank Moved
Rank rose 22 spots (#537 → #515)
2026-11-06
Rank Moved
Rank rose 32 spots (#569 → #537)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.9/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.
Compare with another agent
View MCP Servers Report missing data
69.0
Activity sub-score · out of 100
#299
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 →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
91
Forks
42
Last Push
2026-11-09
yesterday
Commits (4 wk)
92
Downloads (7d)
592
pypi
HN mentions (30d)
—
Open Issues
2
Rank Change
▼7
was #512

Analysis

Activity Inputs

69.0 / 100
StarsRepository reach
11.8 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
24.6 / 25
CommunityFork signal
7.6 / 20

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 4.9/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?
52% 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
Rank 24Grade 8HVTrust 2Scorecard 1Delisted 1Listed 1MCP 1
2026-11-07
Grade Changed
Trust grade C → B
2026-11-07
Rank Moved
Rank rose 22 spots (#537 → #515)
2026-11-06
Rank Moved
Rank rose 32 spots (#569 → #537)
2026-11-05
Rank Moved
Rank dropped 13 spots (#556 → #569)
2026-10-31
Rank Moved
Rank dropped 16 spots (#534 → #550)
2026-10-29
Rank Moved
Rank dropped 17 spots (#521 → #538)
2026-10-28
Grade Changed
Trust grade B → C
2026-10-27
Grade Changed
Trust grade C → B
2026-10-26
Grade Changed
Trust grade B → C
2026-10-21
Rank Moved
Rank rose 11 spots (#514 → #503)
2026-10-18
Grade Changed
Trust grade C → B
2026-10-17
Rank Moved
Rank rose 39 spots (#558 → #519)
2026-10-12
Rank Moved
Rank dropped 17 spots (#545 → #562)
2026-09-30
Grade Changed
Trust grade B → C
2026-09-30
Rank Moved
Rank dropped 45 spots (#469 → #514)
2026-09-27
Rank Moved
Rank dropped 13 spots (#441 → #454)
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)
GitHub → Website → PyPI: redmine-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 65.4 Grade B
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.4 · Raw JSON