Karea MCP Server

karea-mcp npm v0.6.3

Published by starecz — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for Karea task management - 50 tools for Claude Code, Cursor, and other MCP clients to create, edit, close, and recap your dev tasks

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 6

medium Tool "karea_unlink_resource_from_task" can modify the filesystemMTC-CAP-002

Tool "karea_unlink_resource_from_task" can write, overwrite or delete files (keyword "unlink" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool karea_unlink_resource_from_task

medium Tool "karea_unlink_session" can modify the filesystemMTC-CAP-002

Tool "karea_unlink_session" can write, overwrite or delete files (keyword "unlink" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool karea_unlink_session

medium Tool "karea_unlink_jira" can modify the filesystemMTC-CAP-002

Tool "karea_unlink_jira" can write, overwrite or delete files (keyword "unlink" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool karea_unlink_jira

low Mutating tool "karea_unlink_resource_from_task" declares no destructiveHintMTC-CAP-005

Tool "karea_unlink_resource_from_task" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool karea_unlink_resource_from_task

low Mutating tool "karea_unlink_session" declares no destructiveHintMTC-CAP-005

Tool "karea_unlink_session" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool karea_unlink_session

low Mutating tool "karea_unlink_jira" declares no destructiveHintMTC-CAP-005

Tool "karea_unlink_jira" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool karea_unlink_jira

Tools 50

Each tool and what it can reach — statically extracted from the published source.

  • karea_unlink_jirawrites files
  • karea_unlink_resource_from_taskwrites files
  • karea_unlink_sessionwrites files
  • karea_add_noteno sensitive capability
  • karea_add_requisiteno sensitive capability
  • karea_answer_questionno sensitive capability
  • karea_askno sensitive capability
  • karea_close_taskno sensitive capability
  • karea_create_categoryno sensitive capability
  • karea_create_projectno sensitive capability
Show 40 more tools ↓
  • karea_create_questionno sensitive capability
  • karea_create_resourceno sensitive capability
  • karea_create_subtaskno sensitive capability
  • karea_create_taskno sensitive capability
  • karea_delete_categoryno sensitive capability
  • karea_delete_noteno sensitive capability
  • karea_delete_projectno sensitive capability
  • karea_delete_questionno sensitive capability
  • karea_delete_requisiteno sensitive capability
  • karea_delete_resourceno sensitive capability
  • karea_delete_taskno sensitive capability
  • karea_doingno sensitive capability
  • karea_doneno sensitive capability
  • karea_edit_noteno sensitive capability
  • karea_edit_questionno sensitive capability
  • karea_edit_taskno sensitive capability
  • karea_get_contextno sensitive capability
  • karea_get_jira_linkno sensitive capability
  • karea_get_markdownno sensitive capability
  • karea_get_resourceno sensitive capability
  • karea_link_jirano sensitive capability
  • karea_link_resource_to_taskno sensitive capability
  • karea_link_sessionno sensitive capability
  • karea_list_notesno sensitive capability
  • karea_list_projectsno sensitive capability
  • karea_list_questionsno sensitive capability
  • karea_list_resourcesno sensitive capability
  • karea_list_sessionsno sensitive capability
  • karea_list_subtasksno sensitive capability
  • karea_list_tasksno sensitive capability
  • karea_quick_taskno sensitive capability
  • karea_recapno sensitive capability
  • karea_set_contextno sensitive capability
  • karea_set_markdownno sensitive capability
  • karea_share_projectno sensitive capability
  • karea_toggle_requisiteno sensitive capability
  • karea_update_resourceno sensitive capability
  • karea_upload_resourceno sensitive capability
  • karea_view_taskno sensitive capability
  • karea_view_tasksno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.6.3 latest A 96/100 6 1.13.0 2026-09-08

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/karea-mcp/badge.svg)](https://mcptrustchecker.com/registry/karea-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/karea-mcp"><img src="https://mcptrustchecker.com/registry/karea-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/karea-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan karea-mcp --online

Use the free API → How scoring works

More in Productivity & Workflow