2 из последних 2 обновлений изменили то, что читает агент: переписано описаний инструментов — 1, до 2.1.1.
Пакет npm · последняя запись 13 ноября 2026 г. на чистой машине с подставными настройками; отправлялся только tools/list. Изменённое описание — не уязвимость.страница на npm · Метод и ограничения · эти данные в JSON.
Выпуск за выпуском
2.0.0 → 2.1.1
выпуск minor, 4 ноября 2026 г.
sequentialthinking: изменено: описание
До (2.0.0)
A detailed tool for dynamic and reflective problem-solving through thoughts.
This tool helps analyze problems through a flexible thinking process that can adapt and evolve.
Each thought can build on, question, or revise previous insights as understanding deepens.
When to use this tool:
- Breaking down complex problems into steps
- Planning and design with room for revision
- Analysis that might need course correction
- Problems where the full scope might not be clear initially
- Problems that require a multi-step solution
- Tasks that need to maintain context over multiple steps
- Situations where irrelevant information needs to be filtered out
Key features:
- You can adjust total_thoughts up or down as you progress
- You can question or revise previous thoughts
- You can add more thoughts even after reaching what seemed like the end
- You can express uncertainty and explore alternative approaches
- Not every thought needs to build linearly - you can branch or backtrack
- Generates a solution hypothesis
- Verifies the hypothesis based on the Chain of Thought steps
- Repeats the process until satisfied
- Provides a correct answer
Parameters explained:
- thought: Your current thinking step, which can include:
* Regular analytical steps
* Revisions of previous thoughts
* Questions about previous decisions
* Realizations about needing more analysis
* Changes in approach
* Hypothesis generation
* Hypothesis verification
- nextThoughtNeeded: True if you need more thinking, even if at what seemed like the end
- thoughtNumber: Current number in sequence (can go beyond initial total if needed)
- totalThoughts: Current estimate of thoughts needed (can be adjusted up/down)
- isRevision: A boolean indicating if this thought revises previous thinking
- revisesThought: If is_revision is true, which thought number is being reconsidered
- branchFromThought: If branching, which thought number is the branching point
- branchId: Identifier for the current branch (if any)
- needsMoreThoughts: If reaching end but realizing more thoughts needed
You should:
1. Start with an initial estimate of needed thoughts, but be ready to adjust
2. Feel free to question or revise previous thoughts
3. Don't hesitate to add more thoughts if needed, even at the "end"
4. Express uncertainty when present
5. Mark thoughts that revise previous thinking or branch into new paths
6. Ignore information that is irrelevant to the current step
7. Generate a solution hypothesis when appropriate
8. Verify the hypothesis based on the Chain of Thought steps
9. Repeat the process until satisfied with the solution
10. Provide a single, ideally correct answer as the final output
11. Only set nextThoughtNeeded to false when truly done and a satisfactory answer is reached
После (2.1.1)
A detailed tool for dynamic and reflective problem-solving through thoughts.
Each thought can build on, question, or revise previous insights as understanding deepens.
When to use this tool:
- Breaking down complex problems into steps
- Planning and design with room for revision
- Analysis that might need course correction
- Problems where the full scope might not be clear initially
- Tasks that need to maintain context over multiple steps
- Situations where irrelevant information needs to be filtered out
You should:
1. Estimate totalThoughts up front and adjust it up or down as you go; thoughtNumber may exceed it
2. Question or revise earlier thoughts (isRevision with revisesThought), or branch (branchFromThought with branchId)
3. Express uncertainty, and ignore information irrelevant to the current step
4. Generate a solution hypothesis, verify it against the earlier steps, and repeat until satisfied
5. Set nextThoughtNeeded to false only when truly done and a satisfactory answer is reached
1.0.0 → 2.0.0
выпуск major, 19 октября 2026 г.
sequentialthinking: изменено: схема входных данных
Отпечаток — это SHA-256 имени, описания и схемы входных данных инструмента, как его записывает verfy.lock. Тот же отпечаток в вашем lock-файле значит, что агент читает ровно это определение. Verfy 0.16.0 и новее фиксирует также заголовок, аннотации и схему вывода, если сервер их отдаёт, поэтому у такого инструмента в вашем lock-файле отпечаток будет другим.
Инструменты в 2.1.1
Инструмент
Описание
Отпечаток
sequentialthinking
A detailed tool for dynamic and reflective problem-solving through thoughts.
Each thought can build on, question, or revise previous insights as understanding deepens.
When to use this tool:
- Breaking down complex problems into steps
- Planning and design with room for revision
- Analysis that might need course correction
- Problems where the full scope might not be clear initially
- Tasks that need to maintain context over multiple steps
- Situations where irrelevant information needs to be filtered out
You should:
1. Estimate totalThoughts up front and adjust it up or down as you go; thoughtNumber may exceed it
2. Question or revise earlier thoughts (isRevision with revisesThought), or branch (branchFromThought with branchId)
3. Express uncertainty, and ignore information irrelevant to the current step
4. Generate a solution hypothesis, verify it against the earlier steps, and repeat until satisfied
5. Set nextThoughtNeeded to false only when truly done and a satisfactory answer is reached
4549e4c8be39
Зафиксируйте эти инструменты
Зафиксируйте то, что @modelcontextprotocol/server-sequential-thinking отдаёт вам сегодня, закоммитьте lock-файл, и pull request провалится, когда инструмент изменится, с текстом до и после. Зафиксируйте и версию пакета в MCP-конфигурации.
$ pip install verfy
$ verfy lock check --update # показывает каждый инструмент и пишет verfy.lock
$ git add verfy.lock
# .github/workflows/verfy.yml, после actions/checkout- uses: verfy-dev/verfy-action@v1
Поддерживаете этот сервер? Запускайте ту же проверку на своих выпусках и добавьте значок Locked by Verfy в README.