alces-mcp@1.1.0
VERIFIED· startup onlyPublisher claims: "Alces for Jira Data Center — MCP server bridging Jira DC/JSM with AI agents" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Startup only; authenticated tool behavior not tested.- Tested
- server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
- Not tested
- the tool list (the server exited before answering) · what the tools do when called with real credentials
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
ALCES_TOKEN_ESCALATION_DOMAINSJIRA_ADMIN_TOKENJIRA_SESSION_PASSWORDJIRA_USER_TOKENConfiguration, not credentials: ALCES_TOOL_GROUPS, JIRA_SESSION_USERNAME, JIRA_TIMEOUT_MS, JIRA_URL- 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
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Connect it with a scoped credential, under the guard. It asks for ALCES_TOKEN_ESCALATION_DOMAINS, JIRA_ADMIN_TOKEN, JIRA_SESSION_PASSWORD, JIRA_USER_TOKEN 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.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-12 and scored it 85/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 · 47 s · 2 scenarios · 0 deviationsStatic findings
* `.env` only holds a PAT for `admin`, not its real login password, and this endpoint requiresFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* `.env` only holds a PAT for `admin`, not its real login password, and this endpoint requiresFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* against docs/api-specs/jira-jsm-dc.swagger.json. Don't assume it mirrors JQL search's POST.Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.// project's `.env` only holds `admin`'s PAT, not its real login password, so risking a guess thereFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.console.log(cliFlagResult.output);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.* against docs/api-specs/jira-jsm-dc.swagger.json. Don't assume it mirrors JQL search's POST.Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.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
No advisories in OSV for alces-mcp@1.1.0 as of 2d ago. This is the package itself, not its dependencies.