jira-alerts-mcp

MCPattested
v2.1.0io.github.rrvrsApache-2.0Updated 1mo agonpmGitHub

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

Works in
ClaudeCursorCopilotGemini

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.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
229Downloads/wk
4GitHub stars
1mo agoLast update
Reads these credentials
  • JSM_API_TOKENAPI keyoptional

    Atlassian account API token, paired with JSM_EMAIL. Required unless JSM_OAUTH_TOKEN is set.

  • JSM_OAUTH_TOKENOAuth appoptional

    OAuth 3LO or Forge bearer token. Takes precedence over JSM_EMAIL and JSM_API_TOKEN.

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.

Package
Authorio.github.rrvrs
LicenseApache-2.0
Version2.1.0
Sourcenpm+mcp-registry
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · dd11f2b
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface40 tools · 7 privileged
Security scan✓ Cleanv2.0.0 · 1mo agoHow well does this scan work?
EvalsNone
IndexedAug 26, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

40 tools · 7 privileged
Statically extracted from the published packagev2.0.0 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

jsm_list_contactsNo description published

This tool published no description. Forge does not invent one.

jsm_get_contactRead one contact method, including whether it is enabled. Args: - contact_id (string) - response_format ('markdown' | 'json'): default 'markdown' Returns: { "contact": { "id": string, "method": string, "to": string, "status": {...} } }

Read one contact method, including whether it is enabled. Args: - contact_id (string) - response_format ('markdown' | 'json'): default 'markdown' Returns: { "contact": { "id": string, "method": string, "to": string, "status": {...} } }

No input schema was published for this tool.

jsm_create_contactNo description published

This tool published no description. Forge does not invent one.

jsm_update_contactNo description published

This tool published no description. Forge does not invent one.

jsm_delete_contactprivilegedNo description published

This tool published no description. Forge does not invent one.

jsm_list_escalationsNo description published

This tool published no description. Forge does not invent one.

jsm_get_escalationRead one escalation policy: every step, its delay, and who it notifies. Args: - team_id (string), escalation_id (string) - response_format ('markdown' | 'json'): default 'markdown' Returns: { "escalation": { "id": string, "name": string, "rules": [...] } } Delays are measured from the alert ra…

Read one escalation policy: every step, its delay, and who it notifies. Args: - team_id (string), escalation_id (string) - response_format ('markdown' | 'json'): default 'markdown' Returns: { "escalation": { "id": string, "name": string, "rules": [...] } } Delays are measured from the alert ra…

No input schema was published for this tool.

jsm_create_escalationNo description published

This tool published no description. Forge does not invent one.

jsm_update_escalationNo description published

This tool published no description. Forge does not invent one.

jsm_delete_escalationprivilegedNo description published

This tool published no description. Forge does not invent one.

jsm_list_forwarding_rulesNo description published

This tool published no description. Forge does not invent one.

jsm_get_forwarding_ruleRead one forwarding rule: who is forwarding to whom, and for how long. Args: - forwarding_rule_id (string) - response_format ('markdown' | 'json'): default 'markdown' Returns: { "forwarding_rule": { "id": string, "fromUser": {...}, "toUser": {...}, "startDate": string, "endDate": string } }

Read one forwarding rule: who is forwarding to whom, and for how long. Args: - forwarding_rule_id (string) - response_format ('markdown' | 'json'): default 'markdown' Returns: { "forwarding_rule": { "id": string, "fromUser": {...}, "toUser": {...}, "startDate": string, "endDate": string } }

No input schema was published for this tool.

jsm_create_forwarding_ruleNo description published

This tool published no description. Forge does not invent one.

jsm_update_forwarding_ruleChange a forwarding rule's people or its window. Args: - forwarding_rule_id (string): the rule to change - from_user_id, to_user_id, start_date, end_date: all required Returns: { "forwarding_rule": { "id": string, ... } } This is a PUT and takes the whole rule — there is no partial update, so…

Change a forwarding rule's people or its window. Args: - forwarding_rule_id (string): the rule to change - from_user_id, to_user_id, start_date, end_date: all required Returns: { "forwarding_rule": { "id": string, ... } } This is a PUT and takes the whole rule — there is no partial update, so…

No input schema was published for this tool.

jsm_delete_forwarding_ruleprivilegedNo description published

This tool published no description. Forge does not invent one.

jsm_list_schedulesNo description published

This tool published no description. Forge does not invent one.

jsm_list_maintenancesNo description published

This tool published no description. Forge does not invent one.

jsm_get_maintenanceNo description published

This tool published no description. Forge does not invent one.

jsm_create_maintenanceNo description published

This tool published no description. Forge does not invent one.

jsm_update_maintenanceNo description published

This tool published no description. Forge does not invent one.

jsm_delete_maintenanceprivilegedNo description published

This tool published no description. Forge does not invent one.

jsm_list_notification_rulesNo description published

This tool published no description. Forge does not invent one.

jsm_get_notification_ruleRead one notification rule: what it fires on and how it notifies. Args: - notification_rule_id (string) - response_format ('markdown' | 'json'): default 'markdown' Returns: { "notification_rule": { "id": string, "name": string, "actionType": string, "enabled": boolean, "steps": [...] } } The s…

Read one notification rule: what it fires on and how it notifies. Args: - notification_rule_id (string) - response_format ('markdown' | 'json'): default 'markdown' Returns: { "notification_rule": { "id": string, "name": string, "actionType": string, "enabled": boolean, "steps": [...] } } The s…

No input schema was published for this tool.

jsm_create_notification_ruleNo description published

This tool published no description. Forge does not invent one.

jsm_update_notification_ruleChange a notification rule's name, event, order, schedules or enabled flag. Args: - notification_rule_id (string) - name, action_type, enabled: required - order, schedules: optional Returns: { "notification_rule": { "id": string, ... } } Setting enabled=false stops this person being notified…

Change a notification rule's name, event, order, schedules or enabled flag. Args: - notification_rule_id (string) - name, action_type, enabled: required - order, schedules: optional Returns: { "notification_rule": { "id": string, ... } } Setting enabled=false stops this person being notified…

No input schema was published for this tool.

jsm_delete_notification_ruleprivilegedNo description published

This tool published no description. Forge does not invent one.

jsm_list_notification_stepsNo description published

This tool published no description. Forge does not invent one.

jsm_get_notification_stepRead one step of a notification rule. Args: - notification_rule_id (string), step_id (string) - response_format ('markdown' | 'json'): default 'markdown' Returns: { "notification_step": { "id": string, "sendAfter": number, "enabled": boolean, "contact": {...} } }

Read one step of a notification rule. Args: - notification_rule_id (string), step_id (string) - response_format ('markdown' | 'json'): default 'markdown' Returns: { "notification_step": { "id": string, "sendAfter": number, "enabled": boolean, "contact": {...} } }

No input schema was published for this tool.

jsm_create_notification_stepNo description published

This tool published no description. Forge does not invent one.

jsm_update_notification_stepChange a step's contact method, delay or enabled flag. Args: - notification_rule_id (string), step_id (string) - contact_method, contact_to, enabled: required - send_after (number, optional) Returns: { "notification_step": { "id": string, ... } } Disabling a step is silent: the rule still exi…

Change a step's contact method, delay or enabled flag. Args: - notification_rule_id (string), step_id (string) - contact_method, contact_to, enabled: required - send_after (number, optional) Returns: { "notification_step": { "id": string, ... } } Disabling a step is silent: the rule still exi…

No input schema was published for this tool.

jsm_delete_notification_stepprivilegedNo description published

This tool published no description. Forge does not invent one.

jsm_list_overridesNo description published

This tool published no description. Forge does not invent one.

jsm_get_overrideRead one override: who is covering, over what window, and for which rotations. Args: - schedule_id (string), override_alias (string): the alias from jsm_list_overrides, not an id - response_format ('markdown' | 'json'): default 'markdown' Returns: { "override": { "alias": string, "responder": {…

Read one override: who is covering, over what window, and for which rotations. Args: - schedule_id (string), override_alias (string): the alias from jsm_list_overrides, not an id - response_format ('markdown' | 'json'): default 'markdown' Returns: { "override": { "alias": string, "responder": {…

No input schema was published for this tool.

jsm_create_overrideNo description published

This tool published no description. Forge does not invent one.

jsm_update_overrideNo description published

This tool published no description. Forge does not invent one.

jsm_delete_overrideprivilegedNo description published

This tool published no description. Forge does not invent one.

jsm_list_team_rolesNo description published

This tool published no description. Forge does not invent one.

jsm_get_team_roleRead one team role in full, including the rights it grants. Args: - team_id (string), role_id (string) - response_format ('markdown' | 'json'): default 'markdown' Returns: { "team_role": { "id": string, "name": string, "rights": [...] } } Read this before creating or updating a role: rights ar…

Read one team role in full, including the rights it grants. Args: - team_id (string), role_id (string) - response_format ('markdown' | 'json'): default 'markdown' Returns: { "team_role": { "id": string, "name": string, "rights": [...] } } Read this before creating or updating a role: rights ar…

No input schema was published for this tool.

jsm_create_team_roleCreate a role on a team. Args: - team_id (string): the team - name (string): the role name - rights (array): the rights it grants, as the API's own objects Returns: { "team_role": { "id": string, ... } } Synchronous — the response is the created role. Read an existing role with jsm_get_team_…

Create a role on a team. Args: - team_id (string): the team - name (string): the role name - rights (array): the rights it grants, as the API's own objects Returns: { "team_role": { "id": string, ... } } Synchronous — the response is the created role. Read an existing role with jsm_get_team_…

No input schema was published for this tool.

jsm_update_team_roleChange a team role's name or the rights it grants. Args: - team_id (string), role_id (string) - name (string), rights (array) Returns: { "team_role": { "id": string, ... } } IMPORTANT: `rights` replaces the whole list. To add one right you must send the existing ones too — read them with jsm_g…

Change a team role's name or the rights it grants. Args: - team_id (string), role_id (string) - name (string), rights (array) Returns: { "team_role": { "id": string, ... } } IMPORTANT: `rights` replaces the whole list. To add one right you must send the existing ones too — read them with jsm_g…

No input schema was published for this tool.

12 of 40 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

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

Keywords
mcp
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-07 — observed resolution, not a publisher declaration.

60 packages resolved · 4 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

66 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+54 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in project management