three.ws Tutor
NPM · @THREE-WS/TUTOR-MCP · SCANNED SEP 23
Read a Pay-As-You-Learn tutoring session's itemized tab and close it for an attested invoice.
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 Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 553 tokens (~276/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 Tutor MCP server?
three.ws Tutor runs locally as an npm package, launched with npx -y @three-ws/tutor-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/tutor-mcp
claude mcp add nirholas-tutor-mcp -- npx -y @three-ws/tutor-mcp
{
"mcpServers": {
"nirholas-tutor-mcp": {
"command": "npx",
"args": [
"-y",
"@three-ws/tutor-mcp"
]
}
}
} {
"servers": {
"nirholas-tutor-mcp": {
"command": "npx",
"args": [
"-y",
"@three-ws/tutor-mcp"
]
}
}
} codex mcp add nirholas-tutor-mcp -- npx -y @three-ws/tutor-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nirholas-tutor-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@three-ws/tutor-mcp"
],
"enabled": true
}
}
} openclaw mcp add nirholas-tutor-mcp --command npx --arg -y --arg @three-ws/tutor-mcp
mcp_servers:
nirholas-tutor-mcp:
command: "npx"
args: ["-y", "@three-ws/tutor-mcp"] {
"McpServers": {
"nirholas-tutor-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@three-ws/tutor-mcp"
]
}
}
} assistant mcp add nirholas-tutor-mcp -t stdio -c npx -a -y @three-ws/tutor-mcp
{
"mcpServers": {
"nirholas-tutor-mcp": {
"command": "npx",
"args": [
"-y",
"@three-ws/tutor-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.
- 20 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.
- 19 Sept 26 −4
- Stability: pass → 0.77 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.
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/tutor-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 →
close_session Close a tutoring session (finalize invoice) ~186
Finalize a Pay-As-You-Learn tutoring session and return its itemized, attested invoice. Seals the ledger for the given sessionId: status flips to "closed", a SHA-256 attestation is stamped over the line items and total, and no further questions can be billed to this session afterward. Returns sessionId, createdAt, closedAt, questionCount, the full lineItems array, the totalAtomics / totalUsd owed, and the attestation hash. Closing itself is FREE and moves no funds — the learner was already charged per answered question; this only produces the final receipt. Idempotent: closing an already-closed session returns the same total. Use load_session first if you want to review the tab before sealing it.
| Name | Type | Req | Description |
|---|---|---|---|
| sessionId | string | yes | Opaque tutoring session identifier to finalize. Truncated to 100 chars by the API. |
No output schema declared.
No examples provided.
load_session Load a tutoring session ledger ~194
Read the running tab for a Pay-As-You-Learn tutoring session by its sessionId. Returns the itemized ledger: one lineItem per answered question (question text, level, output tokens, per-item cost in USDC atomics and a "$x.xxxxxx" string, and the timestamp), plus the session status ("open" | "closed"), questionCount, and the running totalAtomics / totalUsd. If the session was already closed it also returns the finalized, attested invoice. A sessionId with no stored history returns an empty open session (questionCount 0) rather than an error — that is an honest "nothing billed yet", not a failure. Viewing the tab is always free; this never charges the learner. Read-only live data.
| Name | Type | Req | Description |
|---|---|---|---|
| sessionId | string | yes | Opaque tutoring session identifier (the id the session was opened with). Truncated to 100 chars by the API. |
No output schema declared.
No examples provided.
What is the three.ws Tutor MCP server?
three.ws Tutor is an MCP server listed in the public MCP registry as io.github.nirholas/tutor-mcp. Read a Pay-As-You-Learn tutoring session's itemized tab and close it for an attested invoice. This page covers its npm package (@three-ws/tutor-mcp).
Is the three.ws Tutor MCP server safe to use?
three.ws Tutor scores 80 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 Tutor MCP server expose?
three.ws Tutor exposes 2 tools: load_session, close_session. Their descriptions and schemas cost roughly 380 tokens of context every time the server is loaded.
Is the three.ws Tutor MCP server still maintained?
three.ws Tutor 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.