com.killbottleneck/killbottleneck
NPM · KILLBOTTLENECK-MCP · SCANNED AUG 20
Goal and process maps for humans and AI agents on your own server.
Available components
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 →
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
- 30 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (SEE LICENSE IN LICENSE) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1513 tokens (~100/item across 15 items; 15 tools + 0 resources), lean.Pass
- 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.34.0 and 0.35.0: 3 tool removals, 0 breaking changes, 0 additions. See how to fix → Fail
Tool Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 38% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · killbottleneck-mcp
claude mcp add com-killbottleneck-killbottleneck -- npx -y killbottleneck-mcp
codex mcp add com-killbottleneck-killbottleneck -- npx -y killbottleneck-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-killbottleneck-killbottleneck": {
"type": "local",
"command": [
"npx",
"-y",
"killbottleneck-mcp"
],
"enabled": true
}
}
} openclaw mcp add com-killbottleneck-killbottleneck --command npx --arg -y --arg killbottleneck-mcp
mcp_servers:
com-killbottleneck-killbottleneck:
command: "npx"
args: ["-y", "killbottleneck-mcp"] {
"mcpServers": {
"com-killbottleneck-killbottleneck": {
"command": "npx",
"args": [
"-y",
"killbottleneck-mcp"
]
}
}
} 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.
- 18 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 17 Aug 26 −14
- Stability: unverified → fail ▼ security
- Malware scan: pass → unverified ▼ security
- Tool coverage: 30% → 38% ▲ functional
- Schema quality: 1713 → 1513 ▲ functional
- Package version: 0.34.0 → 0.35.0 functional
- 16 Aug 26 63
First indexed and scored.
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 20 Aug 2026 · Analysed npm/killbottleneck-mcp@0.35.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
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.
add_nodes ~138
Add a subtree of nodes to an existing map under parent_id (or under the apex when parent_id is omitted). A node is a goal; a node with an assignee (owner) OR a deadline IS a task — that is the only kind of task in killBottleneck (there is no separate task record; new work = new node). NOTE: this re-computes the layout of the whole map. Max 200 nodes per call. Returns the updated tree.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| map_id | string | yes | – |
| parent_id | string | – | Existing node id to attach under; omit for apex |
No output schema declared.
No examples provided.
create_map ~116
Create a new goal map from an outline. The map gets an apex (root goal) from `title`/`apex_text`; `outline` items become nested nodes. Layout is computed automatically. Max 200 nodes per call. Returns the created tree with node ids.
| Name | Type | Req | Description |
|---|---|---|---|
| apex_text | string | – | Root goal statement, defaults to title |
| description | string | – | Map description |
| outline | array | yes | Top-level items under the apex, each may have children |
| title | string | yes | Map/project title |
No output schema declared.
No examples provided.
create_rule ~193
Create an automation rule on a map: WHEN trigger fires (and optional AND conditions match) DO the actions in order. Rules run for changes made in the UI, via API and by agents alike. Structural limits: 50 rules per map, 10 actions, 20 conditions — there is NO monthly run quota. A rule applies only to future events, never retroactively. node_id scopes the rule to one node (required for schedule rules whose actions target a node).
| Name | Type | Req | Description |
|---|---|---|---|
| actions | array | yes | 1-10 actions, executed in order |
| conditions | array | – | Optional AND chain checked on the trigger node |
| enabled | boolean | – | Default true |
| map_id | string | yes | – |
| name | string | yes | Human-readable rule name (max 120 chars) |
| node_id | string | – | Optional: scope the rule to one node of the map |
| trigger | object | yes | – |
No output schema declared.
No examples provided.
delete_node ~65
Delete a node INCLUDING its whole subtree. The apex (root) cannot be deleted and whole maps cannot be deleted via the API. Irreversible — read the map first and double-check the node id.
| Name | Type | Req | Description |
|---|---|---|---|
| map_id | string | yes | – |
| node_id | string | yes | – |
No output schema declared.
No examples provided.
delete_rule ~44
Delete an automation rule. Its run log stays (with the rule name snapshot). Irreversible.
| Name | Type | Req | Description |
|---|---|---|---|
| map_id | string | yes | – |
| rule_id | string | yes | – |
No output schema declared.
No examples provided.
delete_rule_template ~42
Delete a rule template from the library (author or admin only). Rules already created from it are independent copies and stay untouched.
| Name | Type | Req | Description |
|---|---|---|---|
| template_id | string | yes | – |
No output schema declared.
No examples provided.
get_map ~61
Read one map as an indented tree with node ids, statuses ([✓] done, [~] in progress, [ ] todo), deadlines and owners. Always call this before modifying a map you have not read yet.
| Name | Type | Req | Description |
|---|---|---|---|
| map_id | string | yes | – |
No output schema declared.
No examples provided.
get_org_structure ~69
Read the organization structure (the org map): positions and functions with node ids, holders and deputies. Use the node ids as dynamic rule targets "position:<nodeId>" / "deputy_of_position:<nodeId>". Read-only — holders and deputies are appointed by an admin in the app.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_maps ~45
List goal maps in the killBottleneck account (id, title, node count, last update). Use archived=true to list archived maps instead.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | – |
No output schema declared.
No examples provided.
list_rule_runs ~87
Read the run log of a map's automation rules (newest first, max 100): what fired, on which node, ok/failed/skipped and what the actions did. skipped = a safety stop (rule chain depth or per-save cap), detail says which.
| Name | Type | Req | Description |
|---|---|---|---|
| map_id | string | yes | – |
| rule_id | string | – | Optional: only runs of this rule |
No output schema declared.
No examples provided.
list_rule_templates ~58
List the instance-wide library of rule templates (shape of a rule without a map or node scope). To use one, read it and call create_rule on the target map with its trigger/conditions/actions — the created rule is an independent copy.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_rules ~62
List automation rules of a map: id, name, enabled, scope node, trigger, conditions, actions, last_fired and last_error (a non-empty last_error means the rule is misconfigured and its owner was notified).
| Name | Type | Req | Description |
|---|---|---|---|
| map_id | string | yes | – |
No output schema declared.
No examples provided.
save_rule_template ~119
Save a rule shape into the instance-wide template library (create, or update with template_id — only the author or an admin may update). Templates carry no map and no node scope; create_subnodes may only use parent=trigger_node. Template names are unique.
| Name | Type | Req | Description |
|---|---|---|---|
| actions | array | yes | – |
| conditions | array | – | – |
| name | string | yes | Unique template name (max 120 chars) |
| template_id | string | – | Update an existing template (author or admin only); omit to create |
| trigger | object | yes | – |
No output schema declared.
No examples provided.
update_node ~290
Update fields of one node: title, status (todo/in_progress/done), description, deadline (YYYY-MM-DD, empty string clears), owner (e-mail, empty string clears), wait_for_children, colour, who performs it (executor_kind / executor_name) and the automation wish (automation_wanted / automation_note). Marking status done may unblock waiting nodes, notify their owners and trigger automations on them.
| Name | Type | Req | Description |
|---|---|---|---|
| automation_note | string | – | Optional context for the automation wish. Empty string clears. |
| automation_wanted | boolean | – | Wish that this step were automated; notifies the AI agent managers. |
| color | string | – | Node colour as #rrggbb, empty string clears |
| deadline | string | – | – |
| description | string | – | – |
| executor_kind | string | – | Who performs the step. Default "human". |
| executor_name | string | – | Which automation handles this step, e.g. "n8n backup" — a record of what exists, not an instruction. Empty string clears. |
| map_id | string | yes | – |
| node_id | string | yes | – |
| owner | string | – | Accountable PERSON (e-mail). Stays a human even for AI/cron steps — this is who gets notified. Empty string clears. |
| status | string | – | – |
| title | string | – | – |
| wait_for_children | boolean | – | – |
No output schema declared.
No examples provided.
update_rule ~124
Update an automation rule. Pass only `enabled` to toggle it on/off; otherwise pass the FULL new shape (name, trigger, actions, optional conditions/node_id) — partial field edits are not merged. Edits apply to future events only and clear the rule's error state.
| Name | Type | Req | Description |
|---|---|---|---|
| actions | array | – | – |
| conditions | array | – | – |
| enabled | boolean | – | – |
| map_id | string | yes | – |
| name | string | – | – |
| node_id | string | – | – |
| rule_id | string | yes | – |
| trigger | object | – | – |
No output schema declared.
No examples provided.