Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.starecz/karea-mcp

NPM · KAREA-MCP · SCANNED SEP 26

Karea task manager - 12 tools covering 69 actions, for Claude Code, Cursor, and other MCP clients.

Available components

−13 this week 67 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability60
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3910 tokens (~325/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability check failed: the tool surface changed between 0.6.1 and 0.10.0: 49 tool removals, 0 breaking changes, 12 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.starecz/karea-mcp server?

io.github.starecz/karea-mcp runs locally as an npm package, launched with npx -y karea-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · karea-mcp

# add to Claude Code
claude mcp add starecz-karea-mcp -- npx -y karea-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "starecz-karea-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "karea-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "starecz-karea-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "karea-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add starecz-karea-mcp -- npx -y karea-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "starecz-karea-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "karea-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add starecz-karea-mcp --command npx --arg -y --arg karea-mcp
# ~/.hermes/config.yaml
mcp_servers:
  starecz-karea-mcp:
    command: "npx"
    args: ["-y", "karea-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "starecz-karea-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "karea-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add starecz-karea-mcp -t stdio -c npx -a -y karea-mcp
// mcp.json
{
  "mcpServers": {
    "starecz-karea-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "karea-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 22 Sept 26 −14
    • Stability: 0.93 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.93 → fail ▼ security
    • Schema quality: 143 → 325 ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Destructive annotations: 0 → pass functional
    • Package version: 0.6.1 → 0.10.0 functional
  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 16 Sept 26 −3
    • Security disclosure: fail → unverified ▼ functional
    • Stability: pass → 0.77 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 Sept 26 0
    • Security disclosure: unverified → fail ▼ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 26 Sept 2026 · Analysed npm/karea-mcp@0.10.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 12 exposed · ~3,910 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
karea_assistant ~186

Ask Karea a natural-language question about your work, or generate a recap of a period. Pass one of these as `action`, with its arguments in `params`: - karea_ask - Send a natural-language request to the Karea AI assistant, which may read or modify your tasks to carry it out, and return its reply. [required: message; optional: projectId] - karea_recap - Return a summary of recent activity (tasks created, closed and updated) over a recent time window. [optional: hours, projectId] For the full parameter schema of any action, call karea_help with that action name.

NameTypeReqDescription
actionstringyesWhich operation to perform. See the list in this tool's description.
paramsobject–Arguments for the chosen action, as an object. Omit for actions that take none.

No output schema declared.

No examples provided.

karea_docs ~275

A task's long-form markdown document and its AI Context (private working memory that survives across sessions). Pass one of these as `action`, with its arguments in `params`: - karea_get_markdown - Read the markdown document attached to a task. [required: task; optional: projectId] - karea_set_markdown - Write the markdown document for a task. [required: task, markdown; optional: projectId, aiSessionId, toolType, sessionLabel] - karea_get_context - Read the task's Context - titled entries of AI working memory that hold the FULL HISTORY of a task (not just its current state): what was tried, decided, discovered, and abandoned along the way. [required: task; optional: projectId] - karea_set_context - Write a titled entry of the task's Context - the AI-facing cross-session working memory. [required: task, context; optional: title, projectId, aiSessionId, toolType, sessionLabel] For the full parameter schema of any action, call karea_help with that action name.

NameTypeReqDescription
actionstringyesWhich operation to perform. See the list in this tool's description.
paramsobject–Arguments for the chosen action, as an object. Omit for actions that take none.

No output schema declared.

No examples provided.

karea_help ~80

Return the full JSON Schema and description of any Karea action, so you can call it correctly through its group tool. Read-only; changes nothing. Omit `action` to list every available action grouped by tool.

NameTypeReqDescription
actionstring–An action name, e.g. "karea_create_task". Omit to list all of them.

No output schema declared.

No examples provided.

karea_integrations ~345

JIRA links on a task, and AI CLI sessions linked to a task. Pass one of these as `action`, with its arguments in `params`: - karea_get_jira_link - Return the linked JIRA issue (key and URL) for a task, if one exists. [required: task; optional: projectId] - karea_link_jira - Link a Karea task to a JIRA issue by issue key (e.g. [required: task, issueKey; optional: projectId] - karea_unlink_jira - Remove the JIRA link from a Karea task [required: task; optional: projectId] - karea_link_session - Link your current AI coding session (Claude Code, OpenCode, Codex, Cursor, Aider) to a Karea task so the user can see the session history for that task and copy a command to resume the session later. [required: task, provider, sessionId; optional: label, projectId] - karea_list_sessions - List AI coding sessions linked to a task (provider, sessionId, label, last active, resume command). [required: task; optional: projectId] - karea_unlink_session - Remove a previously-linked AI session from a task. [required: task, sessionRowId; optional: projectId] For the full parameter schema of any action, call karea_help with that action name.

NameTypeReqDescription
actionstringyesWhich operation to perform. See the list in this tool's description.
paramsobject–Arguments for the chosen action, as an object. Omit for actions that take none.

No output schema declared.

No examples provided.

karea_meetings ~393

Meetings, and the tasks and open questions attached to them. Pass one of these as `action`, with its arguments in `params`: - karea_list_meetings - List meetings. [optional: scope, from, to, projectId] - karea_view_meeting - Return one meeting in full: time, location, project, attendees, prep notes, transcript, linked tasks and linked open questions. [required: meetingId] - karea_create_meeting - Create a meeting. [required: title, startAt, endAt; optional: description, location, projectId, notes, attendees] - karea_edit_meeting - Update a meeting. [required: meetingId; optional: title, startAt, endAt, description, location, projectId, notes, transcript] - karea_delete_meeting - Delete a meeting permanently. [required: meetingId, confirm] - karea_link_task_to_meeting - Link an EXISTING task to a meeting (discussed at / arising from it). [required: meetingId, task; optional: projectId] - karea_unlink_task_from_meeting - Remove the link between a task and a meeting. [required: meetingId, task; optional: projectId] - karea_link_question_to_meeting - Link an EXISTING open question to a meeting, so it is raised there. [required: meetingId, questionId] - karea_unlink_question_from_meeting - Remove the link between an open question and a meeting. [required: meetingId, questionId] For the full parameter schema of any action, call karea_help with that action name.

NameTypeReqDescription
actionstringyesWhich operation to perform. See the list in this tool's description.
paramsobject–Arguments for the chosen action, as an object. Omit for actions that take none.

No output schema declared.

No examples provided.

karea_notes ~431

Notes on a task - human-readable updates the user reads - plus the sticky-note scratch board. For private cross-session memory use karea_docs (set_context). Pass one of these as `action`, with its arguments in `params`: - karea_list_notes - List the notes (human-readable updates) on a task, newest first. [required: task; optional: projectId] - karea_add_note - Add a note to a task - or the same note to many tasks at once, via `tasks`. [required: content; optional: task, tasks, projectId, aiSessionId, toolType, sessionLabel] - karea_edit_note - Change the text of an existing note on a task, by note ID, and return the updated note. [required: task, noteId, content; optional: projectId, aiSessionId, toolType, sessionLabel] - karea_delete_note - Permanently delete a note from a task, by note ID. [required: task, noteId; optional: projectId] - karea_list_sticky_notes - List the user's sticky notes - the scratch pad: short reminders, commands, URLs. [optional: projectId] - karea_create_sticky_note - Pin a short note to the user's sticky board - a command, a URL, a couple of lines to remember. [required: content; optional: title, color, projectId, pinned] - karea_edit_sticky_note - Change a sticky note: its text, title, colour, pin state, or which project it belongs to. [required: noteId; optional: content, title, color, projectId, pinned] - karea_delete_sticky_note - Delete a sticky note. [required: noteId] For the full parameter schema of any action, call karea_help with that action name.

NameTypeReqDescription
actionstringyesWhich operation to perform. See the list in this tool's description.
paramsobject–Arguments for the chosen action, as an object. Omit for actions that take none.

No output schema declared.

No examples provided.

karea_projects ~298

Projects and their categories: list, create, delete, share, and manage the categories inside a project. Pass one of these as `action`, with its arguments in `params`: - karea_list_projects - List all Karea projects with their IDs [no parameters] - karea_create_project - Create a new Karea project owned by you and seed it with the default categories (Coding, Testing, Documenting, Reviewing). [required: name] - karea_delete_project - Permanently delete a project and everything inside it (tasks, categories, notes, history). [required: name; optional: confirm] - karea_share_project - Give another user access to a project by email at a chosen role (owner, editor, commenter or viewer). [required: project, email; optional: role] - karea_create_category - Create a new category (a task bucket) inside an existing project and return it. [required: name; optional: projectId] - karea_delete_category - Permanently delete a category AND every task inside it, including history. [required: name; optional: projectId] For the full parameter schema of any action, call karea_help with that action name.

NameTypeReqDescription
actionstringyesWhich operation to perform. See the list in this tool's description.
paramsobject–Arguments for the chosen action, as an object. Omit for actions that take none.

No output schema declared.

No examples provided.

karea_questions ~300

Open questions: things you are waiting on an answer for. Create, answer, edit, delete. Pass one of these as `action`, with its arguments in `params`: - karea_list_questions - List open questions (unresolved decisions or blockers) in a project, newest first. [optional: projectId, status] - karea_create_question - Create an open question (a decision or blocker to resolve) in a project, optionally linked to tasks, and return it with its short ID (e.g. [required: question; optional: projectId, markdown, taskIds] - karea_answer_question - Answer an open question, located by short ID or text match: sets its answer and flips its status to answered. [required: questionId, answer] - karea_edit_question - Edit an open question: change its text, status (open, answered or cancelled), answer, or linked tasks. [required: questionId; optional: question, answer, status, markdown, taskIdsAdd, taskIdsRemove] - karea_delete_question - Permanently delete an open question. [required: questionId] For the full parameter schema of any action, call karea_help with that action name.

NameTypeReqDescription
actionstringyesWhich operation to perform. See the list in this tool's description.
paramsobject–Arguments for the chosen action, as an object. Omit for actions that take none.

No output schema declared.

No examples provided.

karea_reminders ~254

Reminders: see what is due, create one, snooze it, dismiss it, mark it done. Pass one of these as `action`, with its arguments in `params`: - karea_check_reminders - Return the caller's upcoming and past-due reminders. [optional: taskId, includeDone] - karea_create_reminder - Schedule a reminder on a task. [required: task, fireAt; optional: title, emailOptIn] - karea_snooze_reminder - Snooze a firing reminder by N minutes. [required: reminderId, minutes] - karea_dismiss_reminder - Dismiss a reminder - cancels it so it will not fire again. [required: reminderId] - karea_mark_reminder_done - Fulfill a reminder: closes both the reminder AND the underlying task (status = done). [required: reminderId] For the full parameter schema of any action, call karea_help with that action name.

NameTypeReqDescription
actionstringyesWhich operation to perform. See the list in this tool's description.
paramsobject–Arguments for the chosen action, as an object. Omit for actions that take none.

No output schema declared.

No examples provided.

karea_resources ~377

The file/document library: list, read, create, update, upload, delete, and attach resources to tasks. Pass one of these as `action`, with its arguments in `params`: - karea_list_resources - List resources (text notes & files). [optional: projectId, query, folder, type, mime, minSize, maxSize] - karea_get_resource - Return a resource with its full content and metadata, by ID. [required: resourceId] - karea_create_resource - Create a text resource (a note or document) in a project or folder and return it with its ID. [required: name, content; optional: projectId, folder] - karea_update_resource - Overwrite a text resource content and/or metadata, by ID, and return the updated resource. [required: resourceId; optional: name, content, folder] - karea_upload_resource - Upload a binary file as a resource (base64-encoded) [required: name, data; optional: mimeType, folder, taskId] - karea_delete_resource - Permanently delete a resource (text or file) by ID. [required: resourceId] - karea_link_resource_to_task - Link an existing resource (text or file) to a task. [required: resourceId, task; optional: projectId] - karea_unlink_resource_from_task - Remove the link between a resource and a task. [required: resourceId, task; optional: projectId] For the full parameter schema of any action, call karea_help with that action name.

NameTypeReqDescription
actionstringyesWhich operation to perform. See the list in this tool's description.
paramsobject–Arguments for the chosen action, as an object. Omit for actions that take none.

No output schema declared.

No examples provided.

karea_subtasks ~305

Subtasks and closing requisites - the checklist a task has to satisfy before it can be closed. Pass one of these as `action`, with its arguments in `params`: - karea_create_subtask - Create a subtask under a parent task. [required: parent, title; optional: category, priority, sla, description, markdown, source, closingRequisites, tags, jiraIssueKey, projectId, aiSessionId, toolType, sessionLabel] - karea_list_subtasks - List subtasks of a parent task. [required: parent; optional: projectId] - karea_add_requisite - Add a closing requisite (a checklist item that must be completed before the task may be closed) to a task, and return it. [required: task, description; optional: projectId] - karea_toggle_requisite - Mark a closing requisite complete or incomplete, by ID. [required: task, requisiteId, completed; optional: projectId] - karea_delete_requisite - Permanently delete a closing requisite from a task, by ID. [required: task, requisiteId; optional: projectId] For the full parameter schema of any action, call karea_help with that action name.

NameTypeReqDescription
actionstringyesWhich operation to perform. See the list in this tool's description.
paramsobject–Arguments for the chosen action, as an object. Omit for actions that take none.

No output schema declared.

No examples provided.

karea_tasks ~666

Tasks: find them, read them, create them, change them, close them. The main entry point - start here. Pass one of these as `action`, with its arguments in `params`: - karea_list_tasks - List tasks in a project. [optional: projectId, status, closedSince, limit, category, priority, assignee, search] - karea_view_task - Return one task with all its details (status, priority, deadline, recurrence, category, description, notes, requisites, links), located by visual ID, name or UUID. [required: task; optional: projectId, includeContext] - karea_view_tasks - Return details for MANY tasks in one response. [required: tasks; optional: projectId, includeContext, includeMarkdown] - karea_create_task - Create a new task in a project and return it with its visual ID (e.g. [required: name; optional: category, priority, sla, description, markdown, source, closingRequisites, tags, parentId, jiraIssueKey, projectId, aiSessionId, toolType, sessionLabel] - karea_edit_task - Update fields of an existing task (title, status, priority, deadline, category, assignee, description, tags, or add a note) located by visual ID, name or UUID. [required: task; optional: name, priority, status, sla, description, markdown, category, note, tags, clearTags, closingRequisites, clearClosingRequisites, jiraIssueKey, linkTasks, linkType, unlinkTasks, projectId, aiSessionId, toolType, sessionLabel] - karea_edit_tasks - Apply the SAME change to many tasks in ONE request - status, priority, category, deadline, assignee, or a note. [required: tasks; optional: projectId, status, priority, category, sla, note] - karea_close_task - Mark a task as done: sets status to done and stamps the close time. [required: task; optional: resolution, projectId, aiSessionId, toolType, sessionLabel] - karea_delete_task - Permanently delete a task and its history. [required: task; optional: confirm, projectId] - karea_quick_task - Log something you already finished as a done task (it shows up in Recap) and return it. [required:…

NameTypeReqDescription
actionstringyesWhich operation to perform. See the list in this tool's description.
paramsobject–Arguments for the chosen action, as an object. Omit for actions that take none.

No output schema declared.

No examples provided.

Common questions

What is the io.github.starecz/karea-mcp server?

io.github.starecz/karea-mcp is listed in the public MCP registry as io.github.starecz/karea-mcp. Karea task manager - 12 tools covering 69 actions, for Claude Code, Cursor, and other MCP clients. This page covers its npm package (karea-mcp).

Is the io.github.starecz/karea-mcp server safe to use?

io.github.starecz/karea-mcp scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.starecz/karea-mcp server expose?

io.github.starecz/karea-mcp exposes 12 tools: karea_projects, karea_tasks, karea_subtasks, karea_notes, karea_docs, and 7 more. Their descriptions and schemas cost roughly 3,910 tokens of context every time the server is loaded.

Is the io.github.starecz/karea-mcp server still maintained?

io.github.starecz/karea-mcp is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.starecz/karea-mcp server under?

io.github.starecz/karea-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.