com.moosejudge/alces-mcp

com.moosejudge/alces-mcpv1.1.0Productivity & Project Mgmt

Alces for Jira Data Center — MCP server bridging Jira DC/JSM with AI agents

The current version, v1.1.0, was published to the official MCP registry on 2026-09-22. It is distributed as alces-mcp on npm, filed under Productivity & Project Mgmt by this index, and declares 8 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using com.moosejudge/alces-mcp in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire

Auditable install path →Watch it hold a drift →

Trust verdict · v1 advisory · method

REVIEWstatus: PARTIALfresh until 2026-10-03 00:38 UTC

screened 2026-08-12tier: scannedgranularity: description-levelsource: registry

Semantic screen found no manipulation pattern in the description. Conformance probe not yet run.

mcpindex.integrity.descriptionpassINFO

evidence“No malicious instructions found”via static_description

Limits of this verdict

- Semantic screen only - the deterministic conformance probe has not run on this server
- Confidence is reported but not yet calibrated (v1)
- Screen reads the tool description, not the live behavior
- advisory
- registry description only no input schema
- screen model 8b
- Still current: the description we screened is unchanged, re-checked against the registry
- The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not

Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-09-26).

Contracts can change after screening, with no version bump. The gate pins com.moosejudge/alces-mcp’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Cite this record

People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.

Markdown

[Independent trust record for com.moosejudge/alces-mcp](https://mcpindex.ai/server/com-moosejudge-alces-mcp) - screening verdict, registry provenance, and contract drift monitoring.

HTML

<a href="https://mcpindex.ai/server/com-moosejudge-alces-mcp">Independent trust record for com.moosejudge/alces-mcp</a> - screening verdict, registry provenance, and contract drift monitoring.

Embed this badge

A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.

Markdown

[![mcpindex](https://mcpindex.ai/api/v1/badge/com-moosejudge-alces-mcp)](https://mcpindex.ai/server/com-moosejudge-alces-mcp)

HTML

<a href="https://mcpindex.ai/server/com-moosejudge-alces-mcp"><img src="https://mcpindex.ai/api/v1/badge/com-moosejudge-alces-mcp" alt="mcpindex verdict" height="20" /></a>

Environment variables

JIRA_URL

required

Base URL of the Jira Data Center instance

JIRA_USER_TOKEN

requiredsecret

Personal Access Token for standard operations

JIRA_ADMIN_TOKEN

secret

Personal Access Token for elevated/admin operations (optional)

JIRA_TIMEOUT_MS

Timeout in milliseconds for every Jira API call. Defaults to 30000 (30s) when unset or blank; raise it if your instance is slow.

ALCES_TOOL_GROUPS

Comma-separated tool domains to pre-activate at startup instead of the core-issues default (core-issues, jsm-service-desk, assets, issue-detail, agile, projects, filters-personal-settings, users-groups-permissions, admin). Unknown names are warned about on stderr and ignored.

ALCES_TOKEN_ESCALATION_DOMAINS

Comma-separated tool domains allowed to substitute JIRA_ADMIN_TOKEN via token escalation. Empty by default — no tool may escalate until its domain is listed here.

JIRA_SESSION_USERNAME

Optional Jira DC account username (not a PAT), paired with JIRA_SESSION_PASSWORD, enabling session-cookie auth for the legacy avatar upload/crop/finalize tools. Must be the same account as JIRA_USER_TOKEN and must not be an administrator: those tools authenticate as this account rather than the token.

JIRA_SESSION_PASSWORD

secret

Password for JIRA_SESSION_USERNAME. Only used to establish a session cookie for the legacy avatar upload/crop/finalize tools.

MCP quality score · maturity, not trust · methodology

freshness

completeness

installability

documentation

stability

Alternatives in Productivity & Project Mgmt

Jira Alerts (JSM Operations)

io.github.rrvrs/jira-alerts-mcp

MCP server for Jira Service Management Operations — alerts, on-call schedules and responders

Atlassian Rovo MCP Server

com.atlassian/atlassian-mcp-server

Connect to Atlassian Jira, Confluence, Loom, and more to search, create, and manage your work.

My TV Channel

com.my-tv-channel/my-tv-channel

Create and run 24/7 linear TV channels. Import videos by URL; we transcode, schedule and stream.

Install this server

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "alces-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "--",
        "alces-mcp"
      ],
      "env": {
        "JIRA_URL": "<jira_url>",
        "JIRA_USER_TOKEN": "<your-jira_user_token>",
        "JIRA_ADMIN_TOKEN": "<your-jira_admin_token>",
        "JIRA_TIMEOUT_MS": "30000",
        "ALCES_TOOL_GROUPS": "core-issues",
        "ALCES_TOKEN_ESCALATION_DOMAINS": "<alces_token_escalation_domains>",
        "JIRA_SESSION_USERNAME": "<jira_session_username>",
        "JIRA_SESSION_PASSWORD": "<your-jira_session_password>"
      }
    }
  }
}

Cursor (.cursor/mcp.json)

{
  "mcpServers": {
    "alces-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "--",
        "alces-mcp"
      ],
      "env": {
        "JIRA_URL": "<jira_url>",
        "JIRA_USER_TOKEN": "<your-jira_user_token>",
        "JIRA_ADMIN_TOKEN": "<your-jira_admin_token>",
        "JIRA_TIMEOUT_MS": "30000",
        "ALCES_TOOL_GROUPS": "core-issues",
        "ALCES_TOKEN_ESCALATION_DOMAINS": "<alces_token_escalation_domains>",
        "JIRA_SESSION_USERNAME": "<jira_session_username>",
        "JIRA_SESSION_PASSWORD": "<your-jira_session_password>"
      }
    }
  }
}

Cline (cline_mcp_settings.json)

npx -y -- alces-mcp

Claude Code (claude mcp add)

claude mcp add --scope user alces-mcp -- npx -y -- alces-mcp

Gemini CLI (gemini mcp add)

gemini mcp add -s user alces-mcp npx -y -- alces-mcp

Verdict API

curl -s mcpindex.ai/api/v1/trust/server/com-moosejudge-alces-mcp

Free-tier verdict as JSON: decision + dimensions + severity. Call it from your agent before it invokes a tool it just discovered.

Details

version: v1.1.0
category: Productivity & Project Mgmt
verdict expires: 2026-10-03
quality: 85 / 100
operator: moosejudge

Listing

Listed from the official MCP registry. Unclaimed by its maintainer. Maintainer? Email us →

Provenance

Each verdict is bound to a hash of the exact description it judged, so a re-crawl that changes the text produces a new record rather than silently inheriting this one. Verdict history is hash-chained and anchored to Bitcoin via OpenTimestamps (latest confirmed at block 968,499). Verify it yourself.

Links

Repository →