Redmine MCP Server

MCP server connecting AI assistants to Redmine: issues, projects, wikis, time tracking, agile boards, and CRM, with OAut

MCP Servers Python Grade D Listed MIT
37.3/100
Rank #665 of 1283
Compare Redmine MCP Server

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-10 · 2d ago
Recent change
Rank +1

Is Redmine MCP Server safe? Redmine MCP Server scores 37.3/100 (Grade D), ranked #665 of 1283 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 28% of recent commits are signed; last pushed 2026-08-10. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Rank Moved
Rank dropped 29 spots (#634 → #663)
2026-08-08
Newly Listed
First tracked at rank #634
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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.
67.5
Activity sub-score · out of 100
#288

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

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed 2 days ago

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
65
Forks
26
Last Push
2026-08-10
2 days ago
Commits (4 wk)
106
Downloads (7d)
448
pypi
HN mentions (30d)
Open Issues
2
Rank Change
▲1
was #666

Analysis

HVTrust Dimensions vs MCP Servers

37.3 / 100 · 67.0% confidence

Redmine MCP Server MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
1.4 / 25
3.6 below avg 5.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.5 below avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.8
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
7.5 above avg 12.4
AdoptionLog-scaled stars · package downloads
7.9 / 20
2.1 above avg 5.8

Activity Inputs

67.5 / 100
StarsRepository reach
10.9 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
6.7 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
Not available
Signed Commits
28%
of last 100 commits verified

Is Redmine MCP Server safe?

Public trust evidence for Redmine MCP Server is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
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?
No OpenSSF Scorecard data is currently published for Redmine MCP Server. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Redmine MCP Server actively maintained?
Actively maintained. The repository was pushed to within the last 2 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?
28% 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

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.

Reputation Timeline

Signal history
Listed 1Rank 1
2026-08-10
Rank Moved
Rank dropped 29 spots (#634 → #663)
2026-08-08
Newly Listed
First tracked at rank #634

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 37.3 Grade D
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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON