LeashIndex Get the report

Index / devtools

io.github.its-qusai-nasr/jira-admin-mcp

io-github-its-qusai-nasr-jira-admin-mcp declares 78 capabilities across 78 tools, with 2 critical issues.

99/100 exposureHigh exposure

Manifest recorded 2026-10-22 from tools/list answered by the PyPI package jira-admin-mcp==0.1.1 (published to PyPI as jira-admin-mcp, listed in the official MCP registry as io.github.its-qusai-nasr/jira-admin-mcp 0.1.1), run in an isolated container with no network access and placeholder credentials. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 78 tools

78 of 78 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

critical · irreversible-uncapped · 14 of 78 tools

14 tools are classified as irreversible and declare no limit.

high · no-expiry · All 78 tools

78 of 78 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 78 tools

78 of 78 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

high · uncapped-write · 24 of 78 tools

24 tools can modify data and declare no limit.

low · uncapped-read · 40 of 78 tools

40 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
jira_issues_searchread declared
jira_issues_getread declared
jira_issues_createwrite inferred
jira_issues_updatewrite inferred
jira_issues_transitionwrite assumed
jira_issues_assignwrite inferred
jira_issues_get_transitionsread declared
jira_issues_get_createmetaread declared
jira_issues_deletedestructive declared
jira_issues_linkwrite inferred
jira_issues_get_changelogread declared
jira_issues_bulk_createwrite inferred
jira_comments_listread declared
jira_comments_addwrite inferred
jira_users_searchread declared
jira_users_getread declared
jira_groups_listread declared
jira_groups_get_membersread declared
jira_groups_add_userwrite inferred
jira_groups_remove_userdestructive declared
jira_groups_createwrite inferred
jira_groups_deletedestructive declared
jira_projects_listread declared
jira_projects_getread declared
jira_projects_get_statusesread declared
jira_projects_get_rolesread declared
jira_projects_update_rolewrite inferred
jira_projects_get_versionsread declared
jira_projects_create_versionwrite inferred
jira_projects_get_featuresread declared
jira_projects_get_notification_schemeread declared
jira_projects_get_categoriesread declared
jira_permissions_list_schemesread declared
jira_permissions_get_schemeread declared
jira_permissions_add_grantwrite inferred
jira_permissions_assign_schemedestructive declared
jira_fields_searchread declared
jira_fields_get_contextsread declared
jira_fields_get_optionsread declared
jira_fields_manage_optionswrite assumed
jira_fields_create_contextwrite inferred
jira_fields_update_contextwrite inferred
jira_fields_delete_contextdestructive declared
jira_fields_assign_context_projectswrite inferred
jira_fields_remove_context_projectsdestructive declared
jira_fields_add_context_issuetypeswrite inferred
jira_fields_remove_context_issuetypesdestructive declared
jira_fields_get_project_mappingread declared
jira_workflows_searchread declared
jira_workflows_get_schemesread declared
jira_workflows_get_scheme_mappingsread declared
jira_workflows_get_scheme_project_usagesread declared
jira_workflows_set_scheme_issuetypewrite inferred
jira_workflows_delete_scheme_issuetypedestructive declared
jira_workflows_create_scheme_draftwrite inferred
jira_workflows_publish_scheme_draftsend inferred
jira_issuetypes_listread declared
jira_issuetypes_get_schemesread declared
jira_issuetypes_get_scheme_mappingsread declared
jira_screens_listread declared
jira_screens_get_fieldsread declared
jira_screens_get_schemesread declared
jira_bulk_edit_issuesdestructive declared
jira_bulk_transition_issuesdestructive declared
jira_filters_searchread declared
jira_filters_createwrite inferred
jira_filters_getread declared
jira_filters_updatewrite inferred
jira_filters_deletedestructive declared
jira_filters_change_ownerwrite assumed
jira_filters_get_sharesread declared
jira_filters_add_sharewrite inferred
jira_filters_remove_sharedestructive declared
jira_filters_force_add_sharewrite inferred
jira_issue_link_types_listread declared
jira_statuses_searchread declared
jira_tasks_get_statusread declared
jira_tasks_canceldelete inferred
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.