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.

ThinkerWave

PYPI · THINKERWAVE-MCP

Autonomous research agent for hard problems that labels every claim verified, assumption or guess.

Available components

+19 this week 84 Trust /100

Last scanned (22 hours ago)

Scores higher than 87% of PyPI servers

Category Education and Research

Trust breakdown (7 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 → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 13 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to thinkerwave-ai/thinkerwave). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 15 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability58
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 417 tokens (~69/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (83% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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.

  • 4 Nov 26 +1

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

  • 3 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 2 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 1 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 31 Oct 26 −14
    • Malware scan: pass → unverified ▼ security
  • 29 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
  • 27 Oct 26 +1

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

  • 25 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
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 4 Nov 2026 · Analysed pypi/thinkerwave-mcp@0.1.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo thinkerwave-ai/thinkerwave
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/thinkerwave-ai/thinkerwave/.github/workflows/release.yml@refs/tags/v0.1.2
Rekor log index 3332014778
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:27556ddbe58ca258c85626cc4d3bbac40cf29e8e5f6470f9066ef65c46ab3699

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 13 packages
Packages resolved 13
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~277 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. 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 →

Tool Tokens
get_answer ~40

The best answer so far (or the final one), its confidence, and each finding tagged verified / assumption / guess.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

list_files ~26

Files the run produced (charts, tables, notes).

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

read_file ~48

Read one produced file: text files as text (up to 200 KB), images as images (up to 1 MB).

NameTypeReqDescription
idstringyes–
pathstringyes–

No output schema declared.

No examples provided.

run_status ~34

Status of a run: round, best score so far, and why it stopped once finished.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

start_run ~102

Start a ThinkerWave run on a hard, open-ended problem. `given`: facts to keep exactly as written. `standards`: what a good answer must do. `pitfalls`: mistakes to avoid. Returns the run id; runs take several minutes — check back with run_status, then get_answer.

NameTypeReqDescription
given–––
max_rounds–––
pitfalls–––
problemstringyes–
standards–––
NameTypeReqDescription
resultstringyes–

No examples provided.

stop_run ~27

Stop a run. The best answer so far is kept.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the ThinkerWave MCP server?

ThinkerWave runs locally as a PyPI package, launched with uvx thinkerwave-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · thinkerwave-mcp

# add to Claude Code
claude mcp add thinkerwave-ai-thinkerwave -- uvx thinkerwave-mcp
Common questions

What is the ThinkerWave MCP server?

ThinkerWave is an MCP server listed in the public MCP registry as io.github.thinkerwave-ai/thinkerwave. Autonomous research agent for hard problems that labels every claim verified, assumption or guess. This page covers its PyPI package (thinkerwave-mcp).

Is the ThinkerWave MCP server safe to use?

ThinkerWave scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 ThinkerWave MCP server expose?

ThinkerWave exposes 6 tools: start_run, run_status, get_answer, list_files, read_file, stop_run. Their descriptions and schemas cost roughly 277 tokens of context every time the server is loaded.

Is the ThinkerWave MCP server still maintained?

ThinkerWave is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the ThinkerWave MCP server under?

ThinkerWave declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.