# Clear Thought 1.5 > Clear Thought 1.5 is an open-source MCP server from Waldzell AI with one tool, clear_thought, that structures an agent's reasoning through 37 operations such as sequential thinking, mental models and decision frameworks. It runs locally over stdio from npm. - Canonical: https://www.anchorterminal.com/tools/clear-thought - Markdown: https://www.anchorterminal.com/tools/clear-thought.md (~6,050 tokens) - Slim: https://www.anchorterminal.com/tools/clear-thought.min.md (~1,430 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/clear-thought.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-09 ## Overview **Grade F · 36.4/100 · rank #823 of 842 · #2 in Reasoning scaffolds · not agent-ready · confidence medium** ## Assessment One tool covers 37 reasoning operations with no credentials and no network calls in the published build. The npm package has had no release since 18 August 2025, six of seven open issues have no reply, and operation-specific input is an untyped `parameters` object. ## Facts | Field | Value | | --- | --- | | Vendor | Waldzell AI (https://github.com/waldzellai) | | Kind | MCP server | | Category | Reasoning scaffolds (https://www.anchorterminal.com/categories/reasoning) | | Transport | stdio | | Auth | None · No credentials. The server is a local stdio process. The stdio entry point always starts with the default configuration, so Python execution, file persistence and telemetry stay off. | | Pricing | Free (Free · OSS) · Free software under the MIT licence that the owner runs. Nothing to buy and no account. | | x402 | No · Local stdio server with no payment code in the source or the published package (checked 2026-10-09). | | Licence | MIT | | Tools exposed | 1 | | Packages | npm: `@waldzellai/clear-thought-onepointfive` | | Source | https://github.com/waldzellai/clearthought-onepointfive | | Docs | https://github.com/waldzellai/clearthought-onepointfive/blob/main/README.md | | llms.txt | not found | | Last release | 2025-08-18 | | GitHub stars | 53 (as of 2026-10-09) | | npm downloads / week | 80 | | Tool | `clear_thought`, one tool. Required `operation` (enum of 37) and `prompt`. Optional `parameters` (free-form object), `context`, `sessionId` and `advanced`, of which the last three are not read by the 0.2.1 handler | | Operations | Sequential thinking with chain, tree, beam, MCTS and graph patterns, mental models, debugging approaches, decision frameworks, Socratic method, systems thinking, causal and statistical analysis, OODA loop, Ulysses protocol, four notebook operations and three session operations | | Resources | `guide://clear-thought-operations`, `guide://notebook-interaction`, nine `examples://` documents and a `notebook:///{name}` template. The example files are looked up relative to the working directory | | Runtime | Node.js 18 or later, from the npm package `@waldzellai/clear-thought-onepointfive` 0.2.1 (binary `clear-thought`). The repository also has an HTTP entry point built on the Smithery SDK, which the npm package does not ship | | State | In memory for the life of the process, with a limit of 100 thoughts a session. File persistence to `.ct-data` exists and is off by default | | Code execution | `notebook_run_cell` runs JavaScript in `node:vm`, 5 second default timeout, up to 200 executions a notebook. `code_execution` spawns Python with a 10 second timeout only when `allowCodeExecution` is set, which stdio does not expose | | Telemetry | None in the published 0.2.1. Main adds optional Shinzo instrumentation, off by default (`telemetryProvider` none) and inactive without a token | | Releases | 0.2.0 and 0.2.1 on npm, both 18 August 2025. No git tags and no changelog. The server reports version 0.0.5 in its MCP handshake | | Earlier package | `@waldzellai/clear-thought`, last published as 0.0.4 on 27 May 2025 from a separate repository, not marked deprecated on npm | | Capabilities | reasoning.scaffold | | Tags | community, local, open-source, mcp, typescript, no-auth, no-network, single-tool | | JSON | https://www.anchorterminal.com/api/v1/tools/clear-thought.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-09 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 28 | 5.6 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 39 | 6.3 | | Agent ergonomics | 13% | 16.2 | 53 | 8.6 | | Security & auth | 14% | 17.5 | 39 | 6.8 | | Payments & pricing | 10% | 12.5 | 60 | 7.5 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 4 | 0.3 | | Transparency & trust (editorial 58, provenance 13) | 7% | 8.8 | 36 | 3.1 | | Negative events | up to −15 | up to −15 | Seen 2026-10-09. The README and package description state things the code does not support. The package description says 38 operations and the enum has 37, the README shows `mdp_planning` and `decision_networks` calls that the schema rejects, it gives a Docker build with no Dockerfile in the repository (issue #17, open since 9 September 2025), and it describes Python execution as secure and restricted where the code spawns the system interpreter with only a timeout. The README dates from 24 September 2025 and still reads this way, so the smallest deduction applies (https://github.com/waldzellai/clearthought-onepointfive/blob/main/README.md). | -2 | | **Total** | | | | **36.4 → F** | ### Why each score - Reliability 28: Scored as local software, since the owner runs it over stdio. An npm package with Node.js 18 or later stated in `engines`. The README's Docker build has no Dockerfile behind it, which issue #17 has reported since 9 September 2025 (18 of 20). No CI workflow in the repository. Two test files exist, and `npm test` calls vitest, which is not among the declared dependencies (3 of 25). Seven open issues and four open pull requests on 9 October 2026. Issues #25 (5 June 2026) and #27 (25 August 2026) report that the stdio server keeps running after the client disconnects, with no reply, and the repository's own report of 24 September 2025 marks a session persistence fault as critical and active (5 of 25). Two versions, 0.2.0 and 0.2.1, with no changelog and no tags, and the server reports 0.0.5 in its handshake (2 of 15). Version 0.2.1, with no stability declaration found (0). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 39: One tool with a JSON Schema generated from zod, read from the source and the published build since we do not run vendor software. Every operation-specific input sits in a free-form `parameters` object and there is no output schema (14 of 25). The README is Markdown and an operations guide is served as an MCP resource. No llms.txt (5 of 10). The 642-character description lists 27 of the 37 operations by name, leaves out the session, notebook, OODA, Ulysses and PDR operations, and does not say when to use the tool or when not to. The README has a short guide to choosing an operation (7 of 20). `operation` is an enum of 37 and `prompt` is required. Nothing inside `parameters` is typed or constrained (5 of 15). The README has eight call examples, two of which (`mdp_planning` and `decision_networks`) name operations the enum rejects. The nine `examples://` resources are looked up relative to the working directory, so they resolve only when the server starts in its package folder. Error responses are not documented (6 of 15). npm version numbers only, with no changelog (2 of 15). - Agent ergonomics 53: One tool with a 642-character description, about 160 tokens, and a small schema (25). No way to limit or trim output. Responses are indented JSON, and 32 of the 37 operations append an `initialThought` object from an automatic `sequential_thinking` step. The `advanced` flags that appear to control this are not read by the handler (6 of 20). Invalid arguments return an MCP invalid-parameters error carrying the zod message, and failures inside an operation return `{toolOperation, error, success: false}` with `isError` set. Unknown fields in `parameters` are ignored without a warning, and no error list is documented (9 of 20). No `readOnlyHint`, `destructiveHint` or `idempotentHint`. Each call appends to session state, and the automatic seed step uses one of the 100 thoughts a session allows (3 of 20). Two required arguments with defaults for the rest. `sessionId` and `context` are accepted and dropped (10 of 15). - Security & auth 39: No credentials to hold or leak, so the middle band (20). `code_execution` spawns the system Python interpreter with a timeout and no isolation, but only when `allowCodeExecution` is true, and the stdio entry point always starts with false. `notebook_run_cell` is on by default with no switch and runs model-written JavaScript in `node:vm`, which the Node.js documentation says is not a security mechanism. File persistence is off by default (8 of 20). Most output is the model's own input restructured. The server also reads `docs/clear-thought-operations.md` and `../srcbook-examples` relative to the working directory and serves them as resources, and some responses add a line telling the model to run notebook cells with `mcp__ide__executeCode`. No guidance on untrusted content (6 of 15). No per-call log. The `DIAGNOSTIC_ENABLED` variable sets a flag that nothing else in the published build reads (2 of 15). No SECURITY.md, no disclosure contact and no security.txt. GitHub shows no published advisories (1 of 20). The README calls Python execution secure and restricted, and the code shows a plain child process. - Payments & pricing 60: Free, self-hosted software with nothing to buy, so 20 + 20 + 20. No payment protocol (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 4: The latest npm release, 0.2.1, is dated 18 August 2025, 417 days before this check (0). No release in the last 90 days (0). The last commit on main is dated 24 September 2025. Six of the seven open issues have no comment, the oldest of those from 9 September 2025, and pull request #30, a fix for the disconnect fault, has been open since 25 August 2026 with three others open since October 2025 (2 of 25). Not in the official MCP registry (0). A lockfile and a current MCP SDK range (`^1.17.0`), but no CI, a `test` script whose runner is not declared, and committed build output that issue #28 reports as stale (2 of 10). - Transparency & trust 36: MIT, an OSI licence, on npm and in the repository. The `LICENSE` file's copyright line names Anthropic, PBC, carried over from the MCP reference servers, and not the maintainer (28 of 30). No written statement on data handling. The source shows state held in memory, optional file persistence to `.ct-data` that is off by default, and no network calls in the published build. The main handler is one file of about 2,900 lines, so the reading takes effort (15 of 30). No deprecation policy or dated notices, and the earlier `@waldzellai/clear-thought` package is not marked deprecated on npm (0 of 20). The published build has no telemetry. Main adds Shinzo instrumentation that is off by default and needs a token, described in the configuration schema and a commit message and not in the README (15 of 20). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (19 items): https://www.anchorterminal.com/fixes/clear-thought.md (JSON https://www.anchorterminal.com/fixes/clear-thought.json) ### What we couldn't check - unchecked: the Smithery listing at smithery.ai/servers/waldzellai/clear-thought-onepointfive. The page is drawn by script and showed our reader only navigation, so whether a hosted endpoint is live, and its use count, are unknown. - unchecked: the bodies and comment threads of the open issues and pull requests. Only the list pages were read, so the disconnect fault is reported from issue titles and the open fix in pull request #30. - unchecked: behaviour at run time. Nothing was installed or run, so the operation count, the ignored arguments and the working-directory lookups come from reading the source and the published build. - Whether the session persistence fault in the repository's report of 24 September 2025 affects stdio use. The report describes calls that each receive a new session, which matches the HTTP deployment and not a single stdio process. - Who Waldzell AI is in law. No legal entity, website, terms or privacy policy was found. - The lead described the product correctly. Its package description says 38 operations, and the schema has 37. ### Sources - repository source at commit 34b92d0 (README, src, cli, tests, reports, `LICENSE`, `package.json`), read from a shallow clone: (seen 2026-10-09) - repository page, with star, fork, issue and pull request counts: (seen 2026-10-09) - open issues list: (seen 2026-10-09) - open pull requests list: (seen 2026-10-09) - repository security overview: (seen 2026-10-09) - npm registry document with versions and dates: (seen 2026-10-09) - published 0.2.1 package files, read without running them: (seen 2026-10-09) - npm downloads for the week to 4 October 2026: (seen 2026-10-09) - earlier package `@waldzellai/clear-thought` on npm: (seen 2026-10-09) - official MCP registry search: (seen 2026-10-09) - Node.js `node:vm` documentation: (seen 2026-10-09) - WaldzellAI organisation page on GitHub: (seen 2026-10-09) ## Who's behind it (provenance 13/100, checked 2026-10-09) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | not found | 0/20 | | Domain age | github.com/waldzellai, no registry record we could read | 0/15 | | Endpoint on the vendor's domain | no hosted endpoint | n/a | | Terms of service | nothing hosted, so the MIT licence stands in | 10/10 | | Privacy policy | nothing hosted, not scored | n/a | | Status page | not found | 0/10 | | Changelog | not found | 0/10 | | security.txt | not found | 0/10 | No legal entity is named. The npm author field reads Waldzell AI, the repository sits in the WaldzellAI organisation on GitHub, and 61 of the 63 commits are by the account glassBead. No vendor domain was found. The GitHub organisation page links no website, so the domain line names the GitHub account and scores no domain age. The `LICENSE` file is the MIT text with the line Copyright (c) 2025 Anthropic, PBC, carried over from the MCP reference servers. The README says the server uses the code of the sequentialthinking server. Software the owner runs, so there is no hosted endpoint, status page, service terms or privacy policy. The project publishes none, and the MIT licence stands in for terms. No changelog file, no git tags and no GitHub security policy. The repository's security page reports no published advisories. The `repository`, `homepage` and `bugs` links in `package.json` point to github.com/waldzellai/clear-thought-onepointfive, which returned 404. The repository is at github.com/waldzellai/clearthought-onepointfive. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service**. Nothing is hosted by the vendor, so there are no terms of service to read. The MIT licence stands in and the check scores in full. **Privacy policy**. Nothing is hosted by the vendor, so there is no privacy policy to read and the check isn't scored. ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Strengths - One tool with a 642-character description, so the definition costs little context for 37 operations - No credentials, and no network calls or telemetry code in the published 0.2.1 build - Python execution is off by default, and the stdio entry point has no setting that turns it on - Session state can be exported and imported as JSON with `session_export` and `session_import` - MIT licence, with the source and the npm package both public ## Weaknesses - No npm release since 0.2.1 on 18 August 2025 and no commit on main since 24 September 2025 - Six of seven open issues have no reply, among them two reports that the stdio server keeps running after the client disconnects - Operation-specific input is a free-form `parameters` object, and `sessionId`, `context` and `advanced` are accepted but never read - `notebook_run_cell` runs model-written JavaScript in `node:vm`, which the Node.js documentation says is not a security mechanism - The README shows `mdp_planning` and `decision_networks` calls the schema rejects, and a Docker build with no Dockerfile in the repository ## Before you call it (notes for agents) 1. Call `clear_thought` with `operation` and `prompt`. Put everything else in `parameters`, using the field names in the `guide://clear-thought-operations` resource 2. Do not call `mdp_planning` or `decision_networks`. The README shows them, and the tool's operation enum rejects both 3. Expect an extra `initialThought` object on 32 of the 37 operations, and each one uses a slot of the 100-thought session limit 4. Stop the server process yourself when the session ends. Open issues report that it does not exit when the client disconnects 5. Treat `notebook_run_cell` as unsandboxed code execution on the host, and do not pass it code from untrusted content ## Connect Install: ```bash npx @waldzellai/clear-thought-onepointfive ``` Through letme (picks today, calling later): https://letme.dev/clear-thought. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Sequential Thinking (MCP reference server) | B | 62.5 | 386 | reasoning.scaffold | no | https://www.anchorterminal.com/tools/sequential-thinking-reference-server.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - One tool, `clear_thought`, whose `operation` enum has 37 values in the published 0.2.1 build, while the package description says 38. `operation` and `prompt` are required and operation-specific input goes in a free-form `parameters` object (source: ) - npm has two versions, 0.2.0 and 0.2.1, both published on 18 August 2025, and 80 downloads in the week to 4 October 2026 (source: ) - The last commit on main is dated 24 September 2025. The repository has no tags, no changelog, no CI workflow and no SECURITY.md (source: ) - Seven open issues and four open pull requests on 9 October 2026. Six issues have no comment, and issues #25 and #27 report that the stdio server keeps running after the client disconnects (source: ) - The README's `mdp_planning` and `decision_networks` examples name operations that are missing from the enum the server validates against, on main and in the npm build (source: ) - `notebook_run_cell` runs JavaScript cells in `node:vm` with a 5 second default timeout. `code_execution` spawns the system Python only when `allowCodeExecution` is true, and the stdio entry point always starts with the default of false (source: ) - Main adds optional Shinzo telemetry, off by default and needing a token in `SHINZO_TOKEN`. The published 0.2.1 build has no telemetry code and no network calls (source: ) - Not in the official MCP registry. Searches for clear-thought and waldzell returned no servers (source: ) ## Compare - [Clear Thought 1.5 vs Sequential Thinking (MCP reference server)](https://www.anchorterminal.com/compare/clear-thought-vs-sequential-thinking-reference-server.md): F 36.4 vs B 62.5 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page under github.com/waldzellai, or the README of github.com/waldzellai/clearthought-onepointfive. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "clear-thought", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Clear Thought 1.5 on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Clear Thought 1.5 on Anchor Terminal](https://www.anchorterminal.com/badges/clear-thought.svg)](https://www.anchorterminal.com/tools/clear-thought) ``` Plain link: ```html Clear Thought 1.5 on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Clear Thought 1.5 is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/clear-thought-dark.png - Light: https://www.anchorterminal.com/assets/share/clear-thought-light.png