MCP Server for Lychee Redmine (ssoma-dev/mcp-server-lychee-redmine) is an MCP server listed on the M8ven Trust Index. It scores 56 out of 100, grade D. It declares 8 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
56/100

MCP Server for Lychee Redmine

Enables AI assistants like Claude to interact with Lychee Redmine project management systems through API integration, allowing natural language access to project data and operations.

→ ssoma-dev/mcp-server-lychee-redmine· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

ssoma-dev

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Known vulnerabilities in dependencies: 1 critical, 12 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 1 credential: LYCHEE_REDMINE_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes8 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

search_issues

Search issues in Lychee Redmine. Filter by project, status, assignee, or keyword. Supports pagination.

create_issue

Create a new issue in Lychee Redmine. Requires project_id and subject. Optional: description, priority, assignee, due date.

update_issue

Update an existing issue in Lychee Redmine. Partial updates supported - only specify fields to change.

get_projects

Get list of accessible projects from Lychee Redmine. Supports pagination.

get_project

Get project details by ID from Lychee Redmine. Returns project name, description, status, and members.

get_schedule

Get schedule information for a project in Lychee Redmine. Returns start/end dates, progress, milestones, dependencies, and optional critical path analysis.

get_users

Get list of users from Lychee Redmine. Filter by status (active, locked, all). Supports pagination.

get_project_members

Get members and their roles for a specific project in Lychee Redmine. Includes user and group memberships. Supports pagination.

// known CVEs in dependencies1 critical12 high6 medium12 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@2.1.9GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

high@modelcontextprotocol/sdk@1.0.4GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

highaxios@1.13.2GHSA-35jp-ww65-95wh

axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`

highaxios@1.13.2GHSA-3g43-6gmg-66jw

axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollution Gadget in Config Merge

highaxios@1.13.2GHSA-43fc-jf86-j433

Axios is Vulnerable to Denial of Service via __proto__ Key in mergeConfig

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configLOG_LEVEL(Optional) Log level: DEBUG, INFO, WARN, ERROR (default: INFO)
🔐 secretLYCHEE_REDMINE_API_KEYYour Redmine API key
configLYCHEE_REDMINE_URLYour Lychee Redmine instance URL (HTTPS required)
configRETRY_MAX_ATTEMPTS
configTIMEOUT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

8/8 tools missing one or more hints — search_issues (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); create_issue (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); update_issue (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +5 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Production dependencies are patched

0 critical, 12 high severity in production deps — @modelcontextprotocol/sdk@1.0.4 (high), axios@1.13.2 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

1 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/ssoma-dev/mcp-server-lychee-redmine?variant=verified)](https://m8ven.ai/mcp/ssoma-dev/mcp-server-lychee-redmine)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 2414e3247f7d5d9f4fa9fc1e58cb71383688f9cb
code hash: ac61ff35c1c445ea779682294da5fbce2e411fdd767ea6b7c9a06b73d16e9079
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client