Ikenga iyke (control bridge)
NPM · @IKENGA/MCP-IYKE · SCANNED SEP 20
Drive a running Ikenga desktop app from MCP clients — DOM, click, type, navigate, screenshot.
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 → 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 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to ikenga-hq/ikenga-pkgs). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 30 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 6863 tokens (~90/item across 76 items; 76 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage75
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 26% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "iyke_iframe_send" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 76 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
How do I install the Ikenga iyke (control bridge) MCP server?
Ikenga iyke (control bridge) runs locally as an npm package, launched with npx -y @ikenga/mcp-iyke. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @ikenga/mcp-iyke
claude mcp add dev-ikenga-mcp-iyke -- npx -y @ikenga/mcp-iyke
{
"mcpServers": {
"dev-ikenga-mcp-iyke": {
"command": "npx",
"args": [
"-y",
"@ikenga/mcp-iyke"
]
}
}
} {
"servers": {
"dev-ikenga-mcp-iyke": {
"command": "npx",
"args": [
"-y",
"@ikenga/mcp-iyke"
]
}
}
} codex mcp add dev-ikenga-mcp-iyke -- npx -y @ikenga/mcp-iyke
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-ikenga-mcp-iyke": {
"type": "local",
"command": [
"npx",
"-y",
"@ikenga/mcp-iyke"
],
"enabled": true
}
}
} openclaw mcp add dev-ikenga-mcp-iyke --command npx --arg -y --arg @ikenga/mcp-iyke
mcp_servers:
dev-ikenga-mcp-iyke:
command: "npx"
args: ["-y", "@ikenga/mcp-iyke"] {
"McpServers": {
"dev-ikenga-mcp-iyke": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@ikenga/mcp-iyke"
]
}
}
} assistant mcp add dev-ikenga-mcp-iyke -t stdio -c npx -a -y @ikenga/mcp-iyke
{
"mcpServers": {
"dev-ikenga-mcp-iyke": {
"command": "npx",
"args": [
"-y",
"@ikenga/mcp-iyke"
]
}
}
} 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.
- 20 Sept 26 0
- Stability: 0.97 → pass security
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
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 Sept 2026 · Analysed npm/@ikenga/mcp-iyke@0.2.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | ikenga-hq/ikenga-pkgs |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/ikenga-hq/ikenga-pkgs/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 2545526583 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:f0953eb7b70ae050cc9739ea9e397bbfd72d3263c9f1698d362da8a7bd1986d213e1bcf2d5737da35a104b398e168fcec5708edaa1dcaa7461f382bf7 |
Background: How many MCP packages publish verified provenance →
Dependencies 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
iyke_project_update ~109
Patch fields on an existing project. Only the fields you pass in `patch` are touched — omit a field to leave it as is. Pass `null` to clear a nullable field (root_path, icon, color, description). `position` controls the project ordering in the activity-bar switcher (lower = earlier). Cannot change `id`; create a new project and migrate instead.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Slug of the project to update. |
| patch | object | yes | – |
No output schema declared.
No examples provided.
iyke_query_cache ~67
Dump the TanStack Query cache: queryKey, status, fetchStatus, isStale, dataUpdatedAt, errorUpdatedAt, error, and a 200-char data preview for each entry. Useful for diagnosing stale data or failed fetches.
| Name | Type | Req | Description |
|---|---|---|---|
| pane | string | – | – |
No output schema declared.
No examples provided.
iyke_scratchpad_append ~78
Append to a scratchpad without overwriting. Creates it if missing. `with_separator=true` (default) inserts a horizontal rule + timestamp between the prior body and the new content.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| name | string | yes | – |
| scope | string | – | – |
| with_separator | boolean | – | – |
No output schema declared.
No examples provided.
iyke_scratchpad_delete ~39
Delete a scratchpad by scope+name. Idempotent.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| scope | string | – | – |
No output schema declared.
No examples provided.
iyke_scratchpad_list ~48
List scratchpads in a scope (defaults to active project). Each entry has id, name, updated_at, and a 200-char preview.
| Name | Type | Req | Description |
|---|---|---|---|
| scope | string | – | – |
No output schema declared.
No examples provided.
iyke_scratchpad_read ~48
Read a scratchpad by scope+name. 404 if missing. Returns id, body, updated_at.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| scope | string | – | – |
No output schema declared.
No examples provided.
iyke_scratchpad_write ~105
Create or replace a project-scoped Markdown scratchpad. Use for plans, handoffs, working context that should outlive a chat. `scope` defaults to the active project (project:<active_id>); pass "workspace" or "pkg:<id>" to opt out. `name` is a slug unique within scope. Body cap 1 MB.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| name | string | yes | – |
| scope | string | – | – |
No output schema declared.
No examples provided.
iyke_screenshot ~79
Capture a PNG screenshot of either the full window or a specific pane. Returns the saved path, dimensions, and byte count. Default writes to ~/.local/share/ikenga/screenshots/.
| Name | Type | Req | Description |
|---|---|---|---|
| out_path | string | – | Override default output path. |
| pane_id | string | – | Required when target=pane. |
| target | string | – | – |
No output schema declared.
No examples provided.
iyke_secret_delete ~78
Delete a secret from the given scope. Same scope semantics as iyke_secret_get. Returns ok even if the key did not exist. Does not touch the legacy unscoped key — to clean up legacy entries, delete the value at the unscoped key directly.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | – |
| scope | string | – | – |
No output schema declared.
No examples provided.
iyke_secret_get ~131
Read a secret from the vault. The scope arg partitions the read: omit it (or pass an empty string) to read from the active project; pass "workspace" to read a cross-project shared secret; pass "project:<id>" or "pkg:<id>" to target a specific partition. Returns the value as a string, or null when the key does not exist in the chosen scope. Falls back transparently to the legacy unscoped key when a scoped value is missing (with a deprecation log on the host).
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | – |
| scope | string | – | – |
No output schema declared.
No examples provided.
iyke_secret_list ~65
List secret KEY NAMES (not values) in a scope. Same scope semantics as iyke_secret_get. Returns sorted bare key names — the scope prefix is stripped. Use to inventory what secrets are stored in a project without revealing values.
| Name | Type | Req | Description |
|---|---|---|---|
| scope | string | – | – |
No output schema declared.
No examples provided.
iyke_secret_set ~101
Write a secret to the vault under the given scope (same scope semantics as iyke_secret_get). Triggers a re-dump of the runtime env-vault file so sidecars and per-call MCP children pick up the new value on next spawn. Use this sparingly — secrets are sensitive and the values land in the user's encrypted Stronghold snapshot.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | – |
| scope | string | – | – |
| value | string | yes | – |
No output schema declared.
No examples provided.
iyke_session_list ~115
List Claude chat sessions. Filter by project (defaults to active); pass include_all=true to list across all projects. Returns at most 50 threads by default (max 200). Each entry has id, title, cwd, project_id, claude_session_id, created_at, updated_at.
| Name | Type | Req | Description |
|---|---|---|---|
| include_all | boolean | – | Skip the project filter entirely. |
| limit | integer | – | – |
| project_id | string | – | Slug of the project to filter by. Omit to use the shell's active project. |
No output schema declared.
No examples provided.
iyke_session_move ~66
Move a chat thread between projects. Metadata-only — does not restart the claude subprocess. The cwd captured at spawn time stays whatever it was. Fails if the target project is unknown or archived.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | – |
| thread_id | string | yes | – |
No output schema declared.
No examples provided.
iyke_session_start_in_project ~162
Mint a new Claude chat thread attached to a project. The shell resolves the project root as the session cwd, builds the layered Claude-config overlay dir (skills + agents + commands + merged .mcp.json) for the spawn, and routes the request through the ACP `session/new` handler. Returns the new thread_id; the actual subprocess spawns lazily on the first prompt — fire `acp_prompt` or open `/sessions/$threadId` in the UI to send the initial message. `initial_prompt` is currently informational only (the bridge does not forward it yet).
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Optional cwd override; defaults to the project root_path. |
| initial_prompt | string | – | – |
| project_id | string | yes | – |
No output schema declared.
No examples provided.
iyke_split ~76
Split the focused pane (or a specific pane via pane_id) into two. "horizontal" splits side-by-side; "vertical" splits top-bottom. Subject to the in-app MAX_LEAVES cap (currently 6).
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | yes | – |
| pane_id | string | – | Optional. Defaults to focused pane. |
No output schema declared.
No examples provided.
iyke_state ~121
Get the current state of the Ikenga desktop app — sidebar mode, focused pane route, and the full pane tree under shell.panes. shell.panes has shape { leaves: [{ id, focused, activeTabIdx, tabs: [{kind,title}] }], tree: <recursive PaneNode> }; use leaves[].id with iyke_focus or iyke_close (pane_id) to operate on a specific pane. Call this before iyke_go / iyke_mode / iyke_focus / iyke_close to check what the user is currently looking at.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
iyke_timer_cancel ~39
Cancel a pending timer by id. No-op if already fired or cancelled. Returns { cancelled: bool }.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
iyke_timer_list ~53
List timers in a scope (defaults to active project). Optional status filter: pending | fired | cancelled. Returns timers sorted by fire_at ascending.
| Name | Type | Req | Description |
|---|---|---|---|
| scope | string | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
iyke_timer_schedule ~180
Schedule a one-shot timer in the active project (or specified scope). Pass either fire_at (absolute epoch-ms) or delay_ms (relative from now), not both. When the timer fires the shell emits an OS notification; if agent_id is set, an entry also lands in that agent's inbox (delivered on its next tool call, 24h TTL).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Registered agent id to deliver an inbox event to on fire. |
| body | string | – | Optional notification body. <=4 KB. |
| delay_ms | integer | – | Fire delay from now, ms. Mutually exclusive with fire_at. |
| fire_at | integer | – | Absolute fire time, unix epoch ms. Mutually exclusive with delay_ms. |
| scope | string | – | – |
| title | string | yes | Notification title. <=300 chars. |
No output schema declared.
No examples provided.
iyke_todo_complete ~40
Mark a todo as done and stamp completed_at. Equivalent to iyke_todo_update with status=done.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
iyke_todo_create ~92
Create a project-scoped todo. Tags are free-form strings; assignee is a free-form name (agent or user). Set blocker_id to mark this todo as blocked by another.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | string | – | – |
| blocker_id | string | – | – |
| body | string | – | – |
| scope | string | – | – |
| tags | array | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
iyke_todo_list ~60
List todos in a scope (defaults to active project). Filter by status, tag, assignee.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | string | – | – |
| scope | string | – | – |
| status | string | – | – |
| tag | string | – | – |
No output schema declared.
No examples provided.
iyke_todo_update ~84
Partial update of a todo. Only supplied fields are changed. Pass status="done" or use iyke_todo_complete for the common case.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | string | – | – |
| blocker_id | string | – | – |
| body | string | – | – |
| id | string | yes | – |
| status | string | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
iyke_type ~82
Type text into an input/textarea/contenteditable element. Specify exactly one of `ref` or `selector`. By default appends; pass `replace=true` to overwrite the existing value.
| Name | Type | Req | Description |
|---|---|---|---|
| pane | string | – | – |
| ref | string | – | – |
| replace | boolean | – | – |
| selector | string | – | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
iyke_wait ~82
Wait until a predicate is satisfied or timeout. Use this after iyke_click / iyke_go to wait for the new state to render, instead of fixed sleeps. Returns { satisfied, elapsed_ms, message? }.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | – |
| pane | string | – | – |
| timeout_ms | integer | – | – |
| value | string | yes | – |
No output schema declared.
No examples provided.
What is the Ikenga iyke (control bridge) MCP server?
Ikenga iyke (control bridge) is an MCP server listed in the public MCP registry as dev.ikenga/mcp-iyke. Drive a running Ikenga desktop app from MCP clients, DOM, click, type, navigate, screenshot. This page covers its npm package (@ikenga/mcp-iyke).
Is the Ikenga iyke (control bridge) MCP server safe to use?
Ikenga iyke (control bridge) scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Ikenga iyke (control bridge) MCP server expose?
Ikenga iyke (control bridge) exposes 76 tools: iyke_state, iyke_go, iyke_mode, iyke_open, iyke_split, and 71 more. Their descriptions and schemas cost roughly 6,863 tokens of context every time the server is loaded.
Is the Ikenga iyke (control bridge) MCP server still maintained?
Ikenga iyke (control bridge) is still listed as active in the MCP registry. We last reached this channel on 20 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 Ikenga iyke (control bridge) MCP server under?
Ikenga iyke (control bridge) declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.