// MCP SERVER RECORD

Jira Dev

Unverified
NPMjira-dev-mcp
CRisk gradenotable
Catalogue entry updated 5 days ago
Auth postureNot probedno remote endpoint probed yet
Tools101 Execute · 3 Write · 6 Read
Worst categoryExecutegrade tracks the peak, not the average
Capability mix
Execute 1Write 3Read 6
What it can reach
Ingests untrusted inputTouches secretsReaches networkRuns codeTouches filesChanges permissionsSends external commsPersistsDeletes dataMoves money
Tools 10
jira_analyze_taskExecuteHighjira_add_commentWriteMediumjira_edit_commentWriteMediumjira_set_project_pathWriteLowjira_download_all_attachmentsReadLow
View all 10 tools
jira_download_attachmentReadLowjira_get_project_pathReadLowjira_my_tasksReadLowjira_read_taskReadLowjira_search_issuesReadLow
Change history
No changes recorded since first scan. Watched servers surface a diff within the hour.
Recommended policy
jira_analyze_taskrequire approval
jira_add_commentrate limit
Read-only toolsallow
Full policy breakdown with enforcement rules →
// RUNNING THIS SERVER
DIRECT INSTALL npx -y jira-dev-mcp

Installed this way, nothing enforces the recommended policy above — calls run exactly as the agent makes them.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.