mcp-server-redmine@1.5.1
VERIFIED· not startedPublisher claims: "Model Context Protocol server for Redmine integration" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
REDMINE_API_KEYREDMINE_PASSWORDConfiguration, not credentials: MCP_DATA_DIR, MCP_HOST, MCP_ISSUER_URL, MCP_PORT, MCP_SESSION_SWEEP_INTERVAL, MCP_SESSION_TTL, MCP_TLS_CERT, MCP_TLS_KEY, MCP_TRANSPORT, OTEL_LOG_LEVEL, REDMINE_CA_CERT, REDMINE_DOWNLOAD_DIR, REDMINE_MAX_RETRIES, REDMINE_REQUEST_TIMEOUT, REDMINE_SSL_VERIFY, REDMINE_URL, REDMINE_USERNAME- Where it talks to
- no vendor host named in the code
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard. It asks for REDMINE_API_KEY, REDMINE_PASSWORD and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
What changed since 1.4.0
vet-skills diff mcp-server-redmine 1.4.0 1.5.1This version reaches for something 1.4.0 did not: 2 new credential variables (REDMINE_API_KEY, REDMINE_PASSWORD). Compared from the two recorded runs, not from source.
- New credential variables
- REDMINE_API_KEY, REDMINE_PASSWORD
1.4.0 was not run in the sandbox (static only); the comparison covers what static analysis recorded only.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-16 and scored it 91/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 10 s · 2 scenarios · 0 deviationsStatic findings
return this.sessions.get(sessionId)?.credentials;Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.No other findings across 5,868 lines in 60 files.
Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
Not checked against OSV yet; the weekly check has not reached this version.