Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.Kastalien-Research/thoughtbox

NPM · @KASTALIEN-RESEARCH/THOUGHTBOX · SCANNED AUG 7

Extended reasoning with structured processes, persistence, and workflow guidance

+23 this week 65 Trust /100
Trust breakdown (6 categories)

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 Security70
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.20.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • Dependency health was assessed across the 90 of 91 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1210 tokens (~67/item across 18 items; 3 tools + 15 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 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
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

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 · @kastalien-research/thoughtbox

# add to Claude Code
claude mcp add kastalien-research-thoughtbox -- npx -y @kastalien-research/thoughtbox
# add to Codex CLI
codex mcp add kastalien-research-thoughtbox -- npx -y @kastalien-research/thoughtbox
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kastalien-research-thoughtbox": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@kastalien-research/thoughtbox"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add kastalien-research-thoughtbox --command npx --arg -y --arg @kastalien-research/thoughtbox
# ~/.hermes/config.yaml
mcp_servers:
  kastalien-research-thoughtbox:
    command: "npx"
    args: ["-y", "@kastalien-research/thoughtbox"]
// mcp.json
{
  "mcpServers": {
    "kastalien-research-thoughtbox": {
      "command": "npx",
      "args": [
        "-y",
        "@kastalien-research/thoughtbox"
      ]
    }
  }
}
Changelog

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.

  • 7 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 5 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Aug 26 +4
    • Stability: unverified → 0.27 functional
  • 2 Aug 26 +17
    • Known CVEs: unverified → fail security
    • Provenance: fail → unverified security
    • Install scripts: pass → unverified security
    • Malware scan: unverified → pass security
    • Maintenance: pass → unverified functional
    • License: pass → unverified functional
    • Dependency health: unverified → partial functional
    • Licence: MIT functional
  • 31 Jul 26 −8
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −24
    • Known CVEs: fail → unverified security
    • Malware scan: pass → unverified security
    • CVE-2026-0621 no longer affects this package security
    • CVE-2026-25536 no longer affects this package security
    • CVE-2025-66414 no longer affects this package security
    • Dependency health: partial → unverified functional
  • 29 Jul 26 +49
    • CVE-2025-66414 affects this package: high security
    • CVE-2026-25536 affects this package: high security
    • CVE-2026-0621 affects this package: high security
    • Known CVEs: unverified → fail security
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Schema quality: unverified → good functional
    • Maintenance: unverified → pass functional
    • Schema quality: unverified → 100 functional
    • License: unverified → pass functional
    • Tool coverage: unverified → 100 functional
    • Licence: MIT functional
  • 28 Jul 26 −28
    • Schema quality: 100 → unverified functional
    • Tool coverage: 100 → unverified functional
    • Dependency health: unverified → partial functional
Diagnostics

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 7 Aug 2026 · Analysed npm/@kastalien-research/[email protected]

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm
Vulnerabilities 3 findings
ID CVE Severity Vector Fix available
GHSA-345p-7cg4-v4c7 CVE-2026-25536 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N yes
GHSA-8r9q-7v3j-jr4g CVE-2026-0621 high yes
GHSA-w48q-cv73-mx4w CVE-2025-66414 high yes
Dependencies 90 packages
Packages resolved 90
Deprecated 90
Stale 30
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools · 3 exposed · ~946 tokens

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.

Tool Tokens
mental_models ~197

Access 15 mental models for structured reasoning. Each model provides a complete prompt with process steps, examples, and pitfalls. Mental models are process scaffolds that tell you HOW to think about a problem, not WHAT to think. They're infrastructure for your reasoning. Operations: - get_model: Retrieve a specific mental model prompt - list_models: List available models (optionally filtered by tag) - list_tags: List all available tags with descriptions - get_capability_graph: Get structured data for knowledge graph initialization Available tags: debugging, planning, decision-making, risk-analysis, estimation, prioritization, communication, architecture, validation Use list_models with a tag filter to discover relevant models for your task. For example, use tag "debugging" when stuck on an issue, or "decision-making" when choosing between options.

NameTypeReqDescription
argsobjectArguments for the operation
operationstringyesThe operation to execute

No output schema declared.

No examples provided.

notebook ~461

Notebook toolhost for literate programming with JavaScript/TypeScript. Create, manage, and execute interactive notebooks with markdown documentation and executable code cells. Each notebook runs in an isolated environment with its own package.json and workspace. ✨ NEW: Pre-structured templates for guided workflows - Use template: "sequential-feynman" for deep learning with Feynman Technique - Templates provide scaffolded cells, metacognitive prompts, and progress tracking - Perfect for complex topics requiring validated understanding Available operations: - create: Create a new notebook (optionally from template) - list: List all active notebooks - load: Load notebook from .src.md file - add_cell: Add cell (title/markdown/code) - update_cell: Update cell content - run_cell: Execute code cell - install_deps: Install npm dependencies - list_cells: List all cells in notebook - get_cell: Get cell details - export: Export notebook to .src.md Common operation examples: Create a blank notebook: { operation: "create", args: { title: "My Analysis", language: "typescript" } } Create from Sequential Feynman template: { operation: "create", args: { title: "React Server Components", language: "typescript", template: "sequential-feynman" } } Add a code cell: { operation: "add_cell", args: { notebookId: "abc123", cellType: "code", content: "console.log('hello')", filename: "example.ts" } } Run a cell: { operation: "run_cell", args: { notebookId: "abc123", cellId: "cell_456" } } List notebooks: { operation: "list", args: {} } For detailed schemas of all operations, see the thoughtbox://notebook/operations resource. When to use: - Writing executable documentation - Building reproducible code examples - Creating step-by-step tutorials - Developing and testing code snippets - Prototyping with immediate feedback - Deep learning workflows (with templates)

NameTypeReqDescription
argsobjectArguments for the operation (varies by operation)
operationstringyesThe notebook operation to execute

No output schema declared.

No examples provided.

thoughtbox ~288

Step-by-step thinking tool for complex problem-solving. Supports flexible reasoning: forward thinking (1→N), backward thinking (N→1), branching, and revision. Adjust your approach dynamically as understanding deepens. Use for: - Multi-step analysis and planning - Problems requiring course correction - Hypothesis generation and testing - System design and architecture decisions Patterns Cookbook: Automatically provided at thought 1 with 6 core reasoning patterns, examples, and best practices. Request anytime with includeGuide parameter.

NameTypeReqDescription
branchFromThoughtintegerBranching point thought number
branchIdstringBranch identifier
includeGuidebooleanRequest the patterns cookbook guide as embedded resource (also provided automatically at thought 1 and final thought)
isRevisionbooleanWhether this revises previous thinking
needsMoreThoughtsbooleanIf more thoughts are needed
nextThoughtNeededbooleanyesWhether another thought step is needed
revisesThoughtintegerWhich thought is being reconsidered
thoughtstringyesYour current thinking step
thoughtNumberintegeryesCurrent thought number (can be 1→N for forward thinking, or N→1 for backward/goal-driven thinking)
totalThoughtsintegeryesEstimated total thoughts needed (for backward thinking, start with thoughtNumber = totalThoughts)

No output schema declared.

No examples provided.