three.ws Assistant Widget
NPM · @THREE-WS/ASSISTANT-MCP · SCANNED SEP 23
Generate a paste-ready embed for a floating 3D avatar chatbot on any website.
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 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 11 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 763 tokens (~381/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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 three.ws Assistant Widget MCP server?
three.ws Assistant Widget runs locally as an npm package, launched with npx -y @three-ws/assistant-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @three-ws/assistant-mcp
claude mcp add nirholas-assistant-widget -- npx -y @three-ws/assistant-mcp
{
"mcpServers": {
"nirholas-assistant-widget": {
"command": "npx",
"args": [
"-y",
"@three-ws/assistant-mcp"
]
}
}
} {
"servers": {
"nirholas-assistant-widget": {
"command": "npx",
"args": [
"-y",
"@three-ws/assistant-mcp"
]
}
}
} codex mcp add nirholas-assistant-widget -- npx -y @three-ws/assistant-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nirholas-assistant-widget": {
"type": "local",
"command": [
"npx",
"-y",
"@three-ws/assistant-mcp"
],
"enabled": true
}
}
} openclaw mcp add nirholas-assistant-widget --command npx --arg -y --arg @three-ws/assistant-mcp
mcp_servers:
nirholas-assistant-widget:
command: "npx"
args: ["-y", "@three-ws/assistant-mcp"] {
"McpServers": {
"nirholas-assistant-widget": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@three-ws/assistant-mcp"
]
}
}
} assistant mcp add nirholas-assistant-widget -t stdio -c npx -a -y @three-ws/assistant-mcp
{
"mcpServers": {
"nirholas-assistant-widget": {
"command": "npx",
"args": [
"-y",
"@three-ws/assistant-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.
- 22 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.
- 19 Sept 26 −3
- Stability: pass → 0.77 functional
- Package version: 0.1.0 → 0.1.1 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 17 Sept 26 −1
- Stability: pass → 0.97 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 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.
- 12 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.
- 11 Sept 26 0
- Package version: 0.1.0 → 0.1.1 functional
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 23 Sept 2026 · Analysed npm/@three-ws/assistant-mcp@0.1.1
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 96 packages
| Packages resolved | 96 |
|---|---|
| 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 →
build_assistant_widget Build a paste-ready three.ws assistant widget embed ~462
Turn a config into a ready-to-embed three.ws assistant widget, a floating 3D avatar chatbot you can drop onto any website. Returns a paste-ready <script> tag (with only the non-default settings as data-* attributes), a standalone frame URL for <iframe> embedding, an equivalent ThreeAssistant.init({...}) JavaScript-API snippet, the visual builder link, and the fully-normalized config. Pure and offline: every field is validated and clamped locally, so a bad value falls back to a safe default and the generated HTML is always well-formed. Call list_assistant_options first to see every avatar, background, mode and attribute you can set.
| Name | Type | Req | Description |
|---|---|---|---|
| accent | string | – | Accent "#hex" color for the widget UI. Default "#f97316". Non-hex values fall back to the default. |
| agent | string | – | A three.ws agent id to drive the assistant, as an alternative to picking an avatar directly. |
| avatar | string | – | Which avatar to show: a three.ws avatar id, a "/avatars/*.glb" path (e.g. "/avatars/selfie-girl.glb"), or a full GLB URL. Omit for the default mannequin. |
| background | string | – | Backdrop behind the avatar: "transparent" (default), a "#hex" color, a preset (ember, ocean, violet, forest, dusk, slate), or "gradient:#aabbcc,#112233,160". Anything else falls back to transparent. |
| badge | boolean | – | Show the small "three.ws" attribution badge. Defaults to on. |
| context | string | – | What the assistant should know about the site (used as its grounding context in chat). |
| greeting | string | – | Opening line the assistant shows on load. |
| mode | string | – | Interaction mode: "chat" (text only), "speak" (voice only), or "both" (default). |
| name | string | – | Display name for the assistant / widget header. |
| position | string | – | Which corner the launcher sits in: "right" (default) or "left". |
| voice | boolean | – | Start with voice on (true) or off (false). Defaults to on. |
No output schema declared.
No examples provided.
list_assistant_options List every three.ws assistant widget option ~90
List everything you can configure on the three.ws assistant widget: the built-in avatars, background presets and grammar, interaction modes, chat lanes (free vs bring-your-own-key), and the full data-* attribute reference table. Call this before build_assistant_widget to know the vocabulary. Read-only and offline.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | Optionally return just one section. Omit to get everything. |
No output schema declared.
No examples provided.
What is the three.ws Assistant Widget MCP server?
three.ws Assistant Widget is an MCP server listed in the public MCP registry as io.github.nirholas/assistant-widget. Generate a paste-ready embed for a floating 3D avatar chatbot on any website. This page covers its npm package (@three-ws/assistant-mcp).
Is the three.ws Assistant Widget MCP server safe to use?
three.ws Assistant Widget scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 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 three.ws Assistant Widget MCP server expose?
three.ws Assistant Widget exposes 2 tools: build_assistant_widget, list_assistant_options. Their descriptions and schemas cost roughly 552 tokens of context every time the server is loaded.
Is the three.ws Assistant Widget MCP server still maintained?
three.ws Assistant Widget is still listed as active in the MCP registry. We last reached this channel on 23 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.