OrchestrUI
NPM · ORCHESTRUI · SCANNED SEP 20
Deterministic UI policy, discovery and audits for coding agents across seven ecosystems.
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 Security100
- 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
- 0 of 4 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to ECD5A/OrchestrUI). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 375 tokens (~53/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage68
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 5% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the OrchestrUI MCP server?
OrchestrUI runs locally as an npm package, launched with npx -y orchestrui. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · orchestrui
claude mcp add ecd5a-orchestrui -- npx -y orchestrui
{
"mcpServers": {
"ecd5a-orchestrui": {
"command": "npx",
"args": [
"-y",
"orchestrui"
]
}
}
} {
"servers": {
"ecd5a-orchestrui": {
"command": "npx",
"args": [
"-y",
"orchestrui"
]
}
}
} codex mcp add ecd5a-orchestrui -- npx -y orchestrui
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ecd5a-orchestrui": {
"type": "local",
"command": [
"npx",
"-y",
"orchestrui"
],
"enabled": true
}
}
} openclaw mcp add ecd5a-orchestrui --command npx --arg -y --arg orchestrui
mcp_servers:
ecd5a-orchestrui:
command: "npx"
args: ["-y", "orchestrui"] {
"McpServers": {
"ecd5a-orchestrui": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"orchestrui"
]
}
}
} assistant mcp add ecd5a-orchestrui -t stdio -c npx -a -y orchestrui
{
"mcpServers": {
"ecd5a-orchestrui": {
"command": "npx",
"args": [
"-y",
"orchestrui"
]
}
}
} 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.
- 19 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.
- 17 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.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 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 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 11 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.
- 9 Sept 26 +11
- Tool safety: pass → unverified ▼ security
- Stability: 0.57 → unverified ▼ security
- Provenance: fail → pass ▲ security
- The attested source repository moved: ECD5A/OrchestrUI security
- Schema quality: 330 → 375 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.3.0 → 0.4.0 functional
- 7 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.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 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/orchestrui@0.4.0
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 | ECD5A/OrchestrUI |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/ECD5A/OrchestrUI/.github/workflows/publish-npm.yml@refs/heads/main |
| Rekor log index | 2771609771 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:15c26653f18afe077f0a85393e44c4c4089777d1fec38c823f4e80fe9335e4aae4169194fdcf45faab4dff14e520b0f7e636e9fb29798fdfd7a9f6ee8 |
Background: How many MCP packages publish verified provenance →
Dependencies 4 packages
| Packages resolved | 4 |
|---|---|
| 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 →
audit_plan Audit an OrchestrUI plan ~79
Score a proposed library plan against the nine OrchestrUI quality and licensing categories.
| Name | Type | Req | Description |
|---|---|---|---|
| existing_stack | array | – | – |
| includes_paid_content | boolean | – | – |
| redistributes_react_bits | boolean | – | – |
| rive_asset_rights | string | – | – |
| selected_libraries | array | – | – |
| verifications | array | – | – |
No output schema declared.
No examples provided.
get_install_instructions Get install instructions ~44
Return an official install command as inert text. This tool never executes shell or package-manager commands.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | – | – |
| library_id | string | yes | – |
No output schema declared.
No examples provided.
get_library_guidance Get library guidance ~34
Return use, avoid, compatibility, legal and official-source guidance for one ecosystem.
| Name | Type | Req | Description |
|---|---|---|---|
| library_id | string | yes | – |
No output schema declared.
No examples provided.
inspect_project Inspect local project metadata ~45
Read bounded package.json, package-lock.json and components.json within the server working directory. Return a HostProfile with evidence; never execute project code.
| Name | Type | Req | Description |
|---|---|---|---|
| relative_path | string | – | – |
No output schema declared.
No examples provided.
list_libraries List OrchestrUI libraries ~41
List the seven supported UI ecosystems and optionally filter by role. Returns metadata only.
| Name | Type | Req | Description |
|---|---|---|---|
| role | string | – | Optional role fragment such as charts or marketing-ui. |
No output schema declared.
No examples provided.
recommend_stack Recommend a minimal UI stack ~77
Compute a minimal UI composition from structured host/task profiles, with task text supported as a legacy inference path.
| Name | Type | Req | Description |
|---|---|---|---|
| constraints | array | – | – |
| existing_stack | array | – | – |
| host_profile | object | – | – |
| rive_asset_rights | string | – | – |
| task | string | – | – |
| task_profile | object | – | – |
No output schema declared.
No examples provided.
search_components Search official component metadata ~55
Search a selected library's public official registry when available, with a verified metadata-only fallback.
| Name | Type | Req | Description |
|---|---|---|---|
| library_id | string | yes | – |
| limit | integer | – | – |
| live | boolean | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
What is the OrchestrUI MCP server?
OrchestrUI is an MCP server listed in the public MCP registry as io.github.ECD5A/orchestrui. Deterministic UI policy, discovery and audits for coding agents across seven ecosystems. This page covers its npm package (orchestrui).
Is the OrchestrUI MCP server safe to use?
OrchestrUI scores 91 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 OrchestrUI MCP server expose?
OrchestrUI exposes 7 tools: inspect_project, list_libraries, recommend_stack, get_library_guidance, search_components, and 2 more. Their descriptions and schemas cost roughly 375 tokens of context every time the server is loaded.
Is the OrchestrUI MCP server still maintained?
OrchestrUI 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 OrchestrUI MCP server under?
OrchestrUI declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.