Alces — MCP server for Atlassian Jira Data Center
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
JIRA_USER_TOKENAPI keyrequiredPersonal Access Token for standard operations
JIRA_ADMIN_TOKENAPI keyoptionalPersonal Access Token for elevated/admin operations (optional)
JIRA_SESSION_PASSWORDAPI keyoptionalPassword for JIRA_SESSION_USERNAME. Only used to establish a session cookie for the legacy avatar upload/crop/finalize tools.
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 68 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Alces — MCP server for Atlassian Jira Data Center
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.