three.ws Loom
NPM · @THREE-WS/LOOM-MCP · SCANNED SEP 20
Browse the community 3D-creation gallery, fetch a creation with its viewer URL, and submit it.
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 8 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 918 tokens (~306/item across 3 items; 3 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 Management83
- Stability observed for 25 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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 Loom MCP server?
three.ws Loom runs locally as an npm package, launched with npx -y @three-ws/loom-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/loom-mcp
claude mcp add nirholas-loom-mcp -- npx -y @three-ws/loom-mcp
{
"mcpServers": {
"nirholas-loom-mcp": {
"command": "npx",
"args": [
"-y",
"@three-ws/loom-mcp"
]
}
}
} {
"servers": {
"nirholas-loom-mcp": {
"command": "npx",
"args": [
"-y",
"@three-ws/loom-mcp"
]
}
}
} codex mcp add nirholas-loom-mcp -- npx -y @three-ws/loom-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nirholas-loom-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@three-ws/loom-mcp"
],
"enabled": true
}
}
} openclaw mcp add nirholas-loom-mcp --command npx --arg -y --arg @three-ws/loom-mcp
mcp_servers:
nirholas-loom-mcp:
command: "npx"
args: ["-y", "@three-ws/loom-mcp"] {
"McpServers": {
"nirholas-loom-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@three-ws/loom-mcp"
]
}
}
} assistant mcp add nirholas-loom-mcp -t stdio -c npx -a -y @three-ws/loom-mcp
{
"mcpServers": {
"nirholas-loom-mcp": {
"command": "npx",
"args": [
"-y",
"@three-ws/loom-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.
- 19 Sept 26 −2
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- Package version: 0.1.1 → 0.1.2 functional
- 17 Sept 26 0
- Stability: pass → 0.97 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.
- 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.
- 10 Sept 26 −2
- Stability: pass → 0.80 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
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/@three-ws/loom-mcp@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 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 →
get_creation Fetch one Loom creation by id ~128
Fetch a single Loom creation by its id. Returns the full record — prompt, glbUrl, previewImageUrl, author, tier, backend, createdAt — together with a `viewer_url` (the /forge/embed orbit+AR viewer for the GLB), an `og_image_url`, and a paste-ready `iframe_snippet` so the model can be previewed inline. Returns a not_found error if no creation has that id. Read-only, no key required.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The creation id (a UUID) from the feed or from a prior submit_creation. |
No output schema declared.
No examples provided.
get_loom_feed Browse the Loom 3D-creation gallery ~198
Browse Loom — the public, world-readable gallery of community-forged 3D creations (a forged GLB plus the prompt that made it and a bit of attribution), returned newest-first. Each creation includes its id, prompt, glbUrl, previewImageUrl, author, tier, backend, createdAt (ms epoch), plus a ready-to-use `viewer_url` (the /forge/embed orbit+AR viewer), `og_image_url`, and a paste-ready `iframe_snippet`. Paginate backwards with `before`: pass the `nextBefore` cursor from the previous page to load older items; a null `nextBefore` means you reached the end. Read-only, no key required.
| Name | Type | Req | Description |
|---|---|---|---|
| before | integer | – | Pagination cursor (ms epoch): return only creations older than this. Pass the prior page's nextBefore. |
| limit | integer | – | How many creations to return (1–120, default 60). |
No output schema declared.
No examples provided.
submit_creation Submit a creation to the Loom gallery ~383
Contribute a forged 3D creation to Loom, the PUBLIC, world-readable community gallery. ⚠️ Anything you submit becomes visible to everyone on the platform, so only post models you intend to share. Requires `prompt` (the text that forged it, ≤1000 chars) and `glbUrl` (an https URL to the GLB, hosted on an allowed domain: three.ws, r2.dev, cloudflarestorage.com, replicate.delivery, githubusercontent.com). Optional: `author` attribution (free text, ≤40 chars — NOT an authenticated identity; defaults to "anon"), `previewImageUrl`, `tier`, and `backend`. No key or account is needed; the endpoint is rate-limited to ~20 submissions per hour per IP. Re-submitting the exact same glbUrl returns the existing creation instead of duplicating it. Returns the stored creation with its id and a ready-to-use viewer_url + iframe_snippet. The only coin this platform references is $THREE — never put any other token in a prompt.
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | Attribution shown on the creation (free text, ≤40 chars). Not an authenticated identity. Defaults to "anon". |
| backend | string | – | Optional name of the forge backend that produced the GLB. |
| glbUrl | string | yes | https URL to the GLB. Must be hosted on an allowed domain: three.ws, r2.dev, cloudflarestorage.com, replicate.delivery, githubusercontent.com. |
| previewImageUrl | string | – | Optional URL of a preview/thumbnail image for the feed. |
| prompt | string | yes | The prompt that forged the model. Required, 1–1000 chars. Shown publicly under the creation. |
| tier | string | – | Optional forge tier/quality label (e.g. the model preset used). |
No output schema declared.
No examples provided.
What is the three.ws Loom MCP server?
three.ws Loom is an MCP server listed in the public MCP registry as io.github.nirholas/loom-mcp. Browse the community 3D-creation gallery, fetch a creation with its viewer URL, and submit it. This page covers its npm package (@three-ws/loom-mcp).
Is the three.ws Loom MCP server safe to use?
three.ws Loom scores 78 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. 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 Loom MCP server expose?
three.ws Loom exposes 3 tools: get_loom_feed, get_creation, submit_creation. Their descriptions and schemas cost roughly 709 tokens of context every time the server is loaded.
Is the three.ws Loom MCP server still maintained?
three.ws Loom 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.