Ikenga iyke (control bridge)
NPM · @IKENGA/MCP-IYKE · SCANNED SEP 24
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 & Transparency48
- 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
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1526 tokens (~80/item across 19 items; 19 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage76
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 29% 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 1 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 19 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 royalti-io-ikenga-pkg-mcp-iyke -- npx -y @ikenga/mcp-iyke
{
"mcpServers": {
"royalti-io-ikenga-pkg-mcp-iyke": {
"command": "npx",
"args": [
"-y",
"@ikenga/mcp-iyke"
]
}
}
} {
"servers": {
"royalti-io-ikenga-pkg-mcp-iyke": {
"command": "npx",
"args": [
"-y",
"@ikenga/mcp-iyke"
]
}
}
} codex mcp add royalti-io-ikenga-pkg-mcp-iyke -- npx -y @ikenga/mcp-iyke
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"royalti-io-ikenga-pkg-mcp-iyke": {
"type": "local",
"command": [
"npx",
"-y",
"@ikenga/mcp-iyke"
],
"enabled": true
}
}
} openclaw mcp add royalti-io-ikenga-pkg-mcp-iyke --command npx --arg -y --arg @ikenga/mcp-iyke
mcp_servers:
royalti-io-ikenga-pkg-mcp-iyke:
command: "npx"
args: ["-y", "@ikenga/mcp-iyke"] {
"McpServers": {
"royalti-io-ikenga-pkg-mcp-iyke": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@ikenga/mcp-iyke"
]
}
}
} assistant mcp add royalti-io-ikenga-pkg-mcp-iyke -t stdio -c npx -a -y @ikenga/mcp-iyke
{
"mcpServers": {
"royalti-io-ikenga-pkg-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.
- 24 Sept 26 −3
- Stability: pass → 0.80 functional
- 23 Sept 26 0
- Stability: 0.97 → pass security
- 22 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.
- 20 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.
- 18 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.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 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.
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 24 Sept 2026 · Analysed npm/@ikenga/mcp-iyke@0.1.2
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 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_click ~75
Click an element. Specify exactly one of `ref` (from iyke_dom), `selector` (CSS), or `text` (innerText match). Refs are most reliable.
| Name | Type | Req | Description |
|---|---|---|---|
| pane | string | – | – |
| ref | string | – | – |
| selector | string | – | – |
| text | string | – | – |
No output schema declared.
No examples provided.
iyke_close ~82
Close a pane (or the focused pane if pane_id omitted). Closes the entire pane and all its tabs — to close a single tab from the in-app keyboard, use ⌘⇧W (⌘W closes the whole pane). Refuses to close the last remaining pane.
| Name | Type | Req | Description |
|---|---|---|---|
| pane_id | string | – | Optional. Defaults to focused pane. |
No output schema declared.
No examples provided.
iyke_devtools ~31
Open Chrome DevTools for the main webview (debug builds only). Returns 503 in production builds.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
iyke_dom ~120
Take an accessibility-tree snapshot of the focused pane. Returns Playwright-style text plus structured JSON. Each interactive element gets a stable ref like e1, e2; pass that ref to iyke_click / iyke_type / iyke_key. Refs invalidate on the next snapshot or page navigation. Use `query` for substring filter, `all=true` to include hidden elements.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Include hidden + aria-hidden elements. |
| pane | string | – | – |
| query | string | – | Substring filter against role/name/value. |
No output schema declared.
No examples provided.
iyke_focus ~74
Focus a specific pane. Provide either pane_id (leaf id from iyke_state response — shell.panes.leaves[].id) or index (1-based DFS leaf index, matching the in-app ⌃1..⌃6 keyboard shortcuts).
| Name | Type | Req | Description |
|---|---|---|---|
| index | integer | – | – |
| pane_id | string | – | – |
No output schema declared.
No examples provided.
iyke_go ~77
Navigate the focused pane to a route path inside the Ikenga desktop app (e.g. "/notes/today"). Path must start with "/". This replaces the focused pane's active tab content; use iyke_open with kind=route to add a new tab instead.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Route path, must start with "/". |
No output schema declared.
No examples provided.
iyke_iframe_send ~76
Send a fire-and-forget postMessage to an iframe pane. The iframe bridge listens for known kinds (e.g. "story-select") and acts on the payload. Use to drive mini-app actions from outside the running app.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | – |
| pane | string | yes | – |
| payload | – | – | – |
No output schema declared.
No examples provided.
iyke_iframe_state ~61
Read the latest published state object for an iframe pane (storyboard cursor, comp current frame, etc.). Iframes call publishState(key, value) from their iyke-bridge to expose runtime state for inspection.
| Name | Type | Req | Description |
|---|---|---|---|
| pane | string | yes | – |
No output schema declared.
No examples provided.
iyke_key ~105
Dispatch a keyboard combo. Use names like "Enter", "Escape", "Tab", "ArrowDown", and modifiers Ctrl/Alt/Shift/Meta separated by + or , (e.g. "Ctrl+S", "Meta+K"). Optional `ref`/`selector` targets a specific element; otherwise the active element receives.
| Name | Type | Req | Description |
|---|---|---|---|
| combo | string | yes | – |
| pane | string | – | – |
| ref | string | – | – |
| selector | string | – | – |
No output schema declared.
No examples provided.
iyke_logs ~76
Read recent console + error logs (last 500) from the running webview. Includes window error and unhandledrejection captures.
| Name | Type | Req | Description |
|---|---|---|---|
| level | string | – | – |
| since | integer | – | Only entries with ts >= this (epoch ms). |
| source | string | – | Filter by pane source ("shell" or leaf id). |
No output schema declared.
No examples provided.
iyke_mode ~60
Switch the activity-bar sidebar mode. Valid modes: app, files, agents, sessions, settings, storyboard, video-engine, canvas-design, image-generator. The first five are core; the rest are mini-apps.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | yes | – |
No output schema declared.
No examples provided.
iyke_network ~54
Read recent fetch + XHR network activity (last 100). Each entry has method, url, status, duration_ms, and error if it failed.
| Name | Type | Req | Description |
|---|---|---|---|
| since | integer | – | – |
| source | string | – | – |
No output schema declared.
No examples provided.
iyke_open ~128
Open a new tab in the focused pane. `kind` selects the view type. For "route" pass `path`; "terminal" optionally `cmd` (a shell command string); "chat" requires `session_id`; "artifact" requires `path`; "mini-app" requires `name`.
| Name | Type | Req | Description |
|---|---|---|---|
| cmd | string | – | For terminal kind. Omit for default login shell. |
| kind | string | yes | – |
| name | string | – | For mini-app kind. |
| path | string | – | For route or artifact kinds. |
| session_id | string | – | For chat kind. |
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_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_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_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 io.github.Royalti-io/ikenga-pkg-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 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 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 Ikenga iyke (control bridge) MCP server expose?
Ikenga iyke (control bridge) exposes 19 tools: iyke_state, iyke_go, iyke_mode, iyke_open, iyke_split, and 14 more. Their descriptions and schemas cost roughly 1,526 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 24 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.