Kaiten (iamtemazhe) MCP Server

mcp-kaiten npm v1.1.0 Source verified

Published by iamtemazhe — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

MCP server for Kaiten — cards, time-logs, boards, comments, users

Trust grade
A
94/100
Last scanned get badge →
Trust
A · 94/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
High
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 = 94/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 − 6 = 94. 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
−6 capability blast radius (high) — client exposure if the model is manipulated

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 3

critical Completed toxic-flow trifecta across toolsMTC-FLOW-002

This server (without client built-ins) exposes a complete data-exfiltration chain: kaiten_get_space → kaiten_list_files ⇒ kaiten_create_comment. Untrusted input is ingested, private data is read, and it can be sent to an external sink — and at least one leg is a direct schema wire (⇒), where a producer's output drops straight into a free-text parameter of the next tool, so the chain needs little agent cooperation. Static analysis proves the primitive exists, not that a specific run will occur.

Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.

Location: flow kaiten_get_space → kaiten_list_files → kaiten_create_comment

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

Tool "kaiten_delete_file" can write, overwrite or delete files (keyword "delete_file" 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 kaiten_delete_file

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

Tool "kaiten_delete_file" 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 kaiten_delete_file

Tools 41

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

  • kaiten_create_commentnetwork egress
  • kaiten_delete_filewrites files
  • kaiten_get_spaceingests untrusted input
  • kaiten_list_filesreads sensitive data
  • kaiten_upload_filenetwork egress
  • kaiten_add_checklist_itemno sensitive capability
  • kaiten_add_tagno sensitive capability
  • kaiten_attach_subtaskno sensitive capability
  • kaiten_create_cardno sensitive capability
  • kaiten_create_checklistno sensitive capability
Show 31 more tools ↓
  • kaiten_create_timelogno sensitive capability
  • kaiten_delete_cardno sensitive capability
  • kaiten_delete_checklistno sensitive capability
  • kaiten_delete_commentno sensitive capability
  • kaiten_delete_timelogno sensitive capability
  • kaiten_detach_subtaskno sensitive capability
  • kaiten_get_boardno sensitive capability
  • kaiten_get_board_cardsno sensitive capability
  • kaiten_get_cardno sensitive capability
  • kaiten_get_card_commentsno sensitive capability
  • kaiten_get_card_timelogsno sensitive capability
  • kaiten_get_checklistno sensitive capability
  • kaiten_get_current_userno sensitive capability
  • kaiten_get_space_cardsno sensitive capability
  • kaiten_get_user_rolesno sensitive capability
  • kaiten_get_user_timelogsno sensitive capability
  • kaiten_list_boardsno sensitive capability
  • kaiten_list_card_typesno sensitive capability
  • kaiten_list_columnsno sensitive capability
  • kaiten_list_custom_propertiesno sensitive capability
  • kaiten_list_lanesno sensitive capability
  • kaiten_list_spacesno sensitive capability
  • kaiten_list_subtasksno sensitive capability
  • kaiten_list_tagsno sensitive capability
  • kaiten_list_usersno sensitive capability
  • kaiten_remove_tagno sensitive capability
  • kaiten_search_cardsno sensitive capability
  • kaiten_update_cardno sensitive capability
  • kaiten_update_checklist_itemno sensitive capability
  • kaiten_update_commentno sensitive capability
  • kaiten_update_timelogno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

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
v1.1.0 latest A 94/100 3 1.13.0 2026-09-07

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 · 94/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-kaiten/badge.svg)](https://mcptrustchecker.com/registry/mcp-kaiten)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-kaiten"><img src="https://mcptrustchecker.com/registry/mcp-kaiten/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-kaiten/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 mcp-kaiten --online

Use the free API → How scoring works

Other implementations of Kaiten 2

Independent packages implementing the same tool, scanned with the same engine. Compare all 3 side by side →

More in Productivity & Workflow