three.ws Brain
NPM · @THREE-WS/BRAIN-MCP · SCANNED AUG 3
List LLM providers and run chat completions through the three.ws multi-provider router.
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- 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 21 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 683 tokens (~341/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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @three-ws/brain-mcp
claude mcp add nirholas-brain-mcp -- npx -y @three-ws/brain-mcp
codex mcp add nirholas-brain-mcp -- npx -y @three-ws/brain-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nirholas-brain-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@three-ws/brain-mcp"
],
"enabled": true
}
}
} openclaw mcp add nirholas-brain-mcp --command npx --arg -y --arg @three-ws/brain-mcp
mcp_servers:
nirholas-brain-mcp:
command: "npx"
args: ["-y", "@three-ws/brain-mcp"] {
"mcpServers": {
"nirholas-brain-mcp": {
"command": "npx",
"args": [
"-y",
"@three-ws/brain-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.
- 2 Aug 26 +45
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: unverified → excellent ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: unverified functional
- Licence: Apache-2.0 functional
- 31 Jul 26 −24
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 42
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@three-ws/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
chat Run a chat completion ~315
Run a chat completion through the three.ws LLM router and get back the full reply as a single message. Pick `provider` from `list_providers` (default `gpt-oss-120b`, a free open-weight model). `messages` is the conversation so far (roles `user`/`assistant`); add system instructions via `system`. The route streams and auto-falls-back across mirrors/free tiers if the chosen model is briefly down — this tool collapses that into one reply and reports the actual route taken, token usage, and timing. Paid first-party flagships (Claude, GPT-4o, o3, Qwen Plus, DeepSeek) need a three.ws API key (set THREE_WS_API_KEY); the free open-weight tiers (GPT-OSS 120B, NVIDIA NIM models) need none. Read-only: a completion does not change any platform state.
| Name | Type | Req | Description |
|---|---|---|---|
| maxTokens | integer | — | Maximum output tokens. Clamped to the chosen model’s ceiling by the router. Defaults to 4096. |
| messages | array | yes | Conversation turns in order, each { role: "user"|"assistant", content }. At least one. |
| provider | string | — | Provider/model key from list_providers (e.g. "claude-sonnet-4-6", "gpt-4o", "deepseek-r1"). Defaults to "gpt-oss-120b". |
| system | string | — | Optional system prompt / instructions prepended to the conversation. |
No output schema declared.
No examples provided.
list_providers List LLM providers and models ~188
List every LLM the three.ws router can run a completion through — one entry per provider/model. Each entry has: `key` (the id you pass to `chat`), `label` (human name), `network` (e.g. Anthropic, OpenAI, DashScope, NVIDIA NIM, IBM watsonx.ai), `tier` (flagship | balanced | fast | reasoning), `maxOutput` (max output tokens), `description`, `available` (true when the server currently holds a working key/route for it), and `requiresAuth` (true when it is a paid first-party model that needs a three.ws API key — set THREE_WS_API_KEY; false for the free open-weight tiers). Call this first to pick a `key` for `chat`. The set is live, so availability moves between calls — not idempotent.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.