MCP100 verdict
Provide a structured tool for iterative problem-solving steps.
MCP100 Assessment
Editorial verdict
Provide a structured tool for iterative problem-solving steps.
Reviewed 2026-07-24 · Next review 2026-10-24
Task Fit
Mapped
Specialized workflows
Trust
Reviewed
A dated editorial review is published on the MCP detail page.
Maintenance
Activity observed
A dated repository or package update is available; editorial maintenance review is still pending.
Popularity
Signals available
Visible usage signals are shown for discovery only, not as proof of safety.
Best for
- Complex planning and debugging that benefits from revisions and branches
- MCP demonstrations with a small single-purpose tool surface
- Local workflows that do not require an external SaaS integration
Not ideal for
- Simple questions where repeated reasoning calls add latency and tokens
- Applications that should not surface or persist detailed reasoning traces
- Workflows needing domain data or external actions
Avoid if
- The host records tool arguments and sensitive reasoning must remain undisclosed
- Strict token or latency budgets cannot tolerate repeated tool calls
- Package execution through npx is prohibited by supply-chain policy
Trade-offs
- Its single-tool scope keeps permissions small but provides no external facts or actions.
- Structured thought history supports revision while increasing context use and potential telemetry exposure.
- The package is easy to run with npx, while stricter environments may require a pinned version or container digest.
Evidence scope
Evidence
Popularity
89.6k shared-repository stars · not MCP-specific
144.4k package downloads
Stars observed 2026-08-14T18:46:26.000Z · Downloads observed 2026-07-29T17:30:00.000Z
Shared repository stars are not MCP-specific.
Exact implementation package metric.
Maintenance
Publisher activity observed 2026-08-10T02:41:59Z
Current source snapshot
Trust review
Source relationship: Ecosystem official
Reviewed 2026-07-24 · Next review 2026-10-24