three.ws Brain
NPM · @THREE-WS/BRAIN-MCP · SCANNED SEP 20
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 → 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 Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 693 tokens (~346/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 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 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 Brain MCP server?
three.ws Brain runs locally as an npm package, launched with npx -y @three-ws/brain-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/brain-mcp
claude mcp add nirholas-brain-mcp -- npx -y @three-ws/brain-mcp
{
"mcpServers": {
"nirholas-brain-mcp": {
"command": "npx",
"args": [
"-y",
"@three-ws/brain-mcp"
]
}
}
} {
"servers": {
"nirholas-brain-mcp": {
"command": "npx",
"args": [
"-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": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@three-ws/brain-mcp"
]
}
}
} assistant mcp add nirholas-brain-mcp -t stdio -c npx -a -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.
- 20 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.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 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.
- 13 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.
- 11 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.
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/brain-mcp@0.1.3
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 →
chat Run a chat completion ~316
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-5, o3, Grok, 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-5", "gpt-5.4", "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 ~195
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, xAI, DashScope, NVIDIA NIM, IBM watsonx.ai), `tier` (flagship | balanced | fast | reasoning | pro | coding), `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.
What is the three.ws Brain MCP server?
three.ws Brain is an MCP server listed in the public MCP registry as io.github.nirholas/brain-mcp. List LLM providers and run chat completions through the three.ws multi-provider router. This page covers its npm package (@three-ws/brain-mcp).
Is the three.ws Brain MCP server safe to use?
three.ws Brain 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 Brain MCP server expose?
three.ws Brain exposes 2 tools: list_providers, chat. Their descriptions and schemas cost roughly 511 tokens of context every time the server is loaded.
Is the three.ws Brain MCP server still maintained?
three.ws Brain 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.