Verfy

MCP-серверы / jupyter-mcp-server

Изменения MCP-инструментов

jupyter-mcp-server

1 из последних 5 обновлений изменили то, что читает агент: переписано описаний инструментов — 2, до 2.2.5.

Пакет PyPI · последняя запись 13 ноября 2026 г. на чистой машине с подставными настройками; отправлялся только tools/list. Изменённое описание — не уязвимость. страница на PyPI · Метод и ограничения · эти данные в JSON.

Выпуск за выпуском

2.2.4 → 2.2.5

выпуск patch, 5 ноября 2026 г.

Определения инструментов не изменились.

2.2.3 → 2.2.4

выпуск patch, 11 октября 2026 г.
connect_to_jupyter: изменено: описание
До (2.2.3)
Connect to a Jupyter server dynamically with URL and token. This tool allows you to connect to different Jupyter servers without needing to restart the MCP server or modify configuration files. Particularly useful when: - Working with multiple Jupyter servers with different ports/tokens - Jupyter server token changes dynamically - Need to switch between different Jupyter instances Example usage: - "Connect to http://localhost:8888 with token abc123" - "Connect to http://localhost:8889 without authentication"
После (2.2.4)
Connect to a Jupyter server dynamically with URL and token. This tool allows you to connect to different Jupyter servers without needing to restart the MCP server or modify configuration files. Particularly useful when: - Working with multiple Jupyter servers with different ports/tokens - Jupyter server token changes dynamically - Need to switch between different Jupyter instances The server is checked first: the tool asks it for `/api/status` with the given token, and if it can't be reached, rejects the token or doesn't answer with a 200, the call fails and the previous connection stays in place. The `local` URL and non-Jupyter document providers are not checked. Example usage: - "Connect to http://localhost:8888 with token abc123" - "Connect to http://localhost:8889 without authentication"
use_notebook: изменено: описание и схема входных данных
До (2.2.3)
Use a notebook and activate it for following cell operations. All cell operations will be performed on the currently activated notebook. Activate new notebook will deactivate the previously activated notebook. Reactivate previously activated notebook using same notebook_name and notebook_path.
После (2.2.4)
Use a notebook and activate it for following cell operations. All cell operations will be performed on the currently activated notebook. Activate new notebook will deactivate the previously activated notebook. Reactivate previously activated notebook using same notebook_name and notebook_path. Kernel selection follows the notebook's existing context. Pass kernel_id to use a kernel that is already running; use_notebook verifies it is alive and creates a Jupyter session for the notebook when no session exists. Without kernel_id, a sandbox already selected with use_sandbox is reused. If none is selected but the notebook already has a live Jupyter session, use_notebook triggers use_sandbox for that session's kernel and reports that in the reply. With neither, no kernel is created. Pass kernel_id=NEW to start an isolated kernel.

2.2.2 → 2.2.3

выпуск patch, 26 сентября 2026 г.

Определения инструментов не изменились.

2.2.1 → 2.2.2

выпуск patch, 21 сентября 2026 г.

Определения инструментов не изменились.

2.2.0 → 2.2.1

выпуск patch, 20 сентября 2026 г.

Определения инструментов не изменились.

Проверенные выпуски: 2.2.0 (2026-09-20); 2.2.1 (2026-09-20); 2.2.2 (2026-09-21); 2.2.3 (2026-09-26); 2.2.4 (2026-10-11); 2.2.5 (2026-11-05).

Инструменты в 2.2.5

Отпечаток — это SHA-256 имени, описания и схемы входных данных инструмента, как его записывает verfy.lock. Тот же отпечаток в вашем lock-файле значит, что агент читает ровно это определение. Verfy 0.16.0 и новее фиксирует также заголовок, аннотации и схему вывода, если сервер их отдаёт, поэтому у такого инструмента в вашем lock-файле отпечаток будет другим.

Инструменты в 2.2.5
ИнструментОписаниеОтпечаток
clear_cell_outputClear the outputs and execution count of a single code cell in the currently activated notebook, without deleting the cell itself.8b95bf70e7f6
connect_to_jupyterConnect to a Jupyter server dynamically with URL and token. This tool allows you to connect to different Jupyter servers without needing to restart the MCP server or modify configuration files. Particularly useful when: - Working with multiple Jupyter servers with different ports/tokens - Jupyter server token changes dynamically - Need to switch between different Jupyter instances The server is checked first: the tool asks it for `/api/status` with the given token, and if it can't be reached, rejects the token or doesn't answer with a 200, the call fails and the previous connection stays in place. The `local` URL and non-Jupyter document providers are not checked. Example usage: - "Connect to http://localhost:8888 with token abc123" - "Connect to http://localhost:8889 without authentication" 81ae0f8ba579
delete_cellDelete specific cells from the currently activated notebook and return the cell source of deleted cells (if include_source=True).8fd3e6db4675
edit_cell_sourcePerform a surgical find-and-replace within a cell's source (like an editor's Edit tool). Finds `old_string` in the cell and replaces it with `new_string`. Matching is literal (not regex) and may span multiple lines. By default, `old_string` must appear exactly once; set `replace_all=True` for multiple occurrences. Returns a diff of the changes made. Prefer this over overwrite_cell_source for small, targeted edits — it is safer because unchanged parts of the cell are left untouched. Use read_cell first to see the current source and construct an accurate old_string.928e74b831ee
execute_cellExecute a cell from the currently activated notebook with timeout and return it's outputsa62c7b28528b
execute_codeExecute code directly in a kernel (not saved to notebook). If `use_sandbox` selected an active sandbox, this tool executes on that sandbox instead of a Jupyter kernel. This allows agents to switch between kernel-backed and sandbox-backed execution using the same execute_code API. Targets the current activated notebook's kernel by default. Pass kernel_id to execute in a specific kernel directly — including raw kernels with no notebook attached. Recommended to use in following cases: 1. Execute Jupyter magic commands(e.g., `%timeit`, `%pip install xxx`) 2. Performance profiling and debugging. 3. View intermediate variable values(e.g., `print(xxx)`, `df.head()`) 4. Temporary calculations and quick tests(e.g., `np.mean(df['xxx'])`) 5. Execute Shell commands in Jupyter server(e.g., `!git xxx`) Under no circumstances should you use this tool to: 1. Import new modules or perform variable assignments that affect subsequent Notebook execution 2. Execute dangerous code that may harm the Jupyter server or the user's data without permission 2d5d96a5f69b
insert_cellInsert a cell to specified position from the currently activated notebook.41beada9dcb1
insert_execute_code_cellInsert a cell at specified index from the currently activated notebook and then execute it with timeout and return it's outputs It is a shortcut tool for insert_cell and execute_cell tools, recommended to use if you want to insert a cell and execute it at the same time8f442426d87b
list_files List all files and directories recursively in the Jupyter server's file system. Used to explore the file system structure of the Jupyter server or to find specific files or directories. 745e5bd11a23
list_kernelsList all available kernels in the Jupyter server. This tool shows all running and available kernel sessions on the Jupyter server, including their IDs, names, states, connection information, and kernel specifications. Useful for monitoring kernel resources and identifying specific kernels for connection. 95624b352715
list_notebooksList all notebooks that have been used via use_notebook tool3c2d4c88090f
move_cellMove a cell from source_index to target_index within the currently activated notebook. The cell is removed from source_index and placed at target_index. Cells in between shift to fill the gap. The cell's type, source, and outputs are preserved. Example: in a notebook [A, B, C, D], move_cell(1, 3) produces [A, C, D, B]. Use this tool instead of manually deleting and re-inserting a cell — it is atomic and preserves cell metadata. Use read_notebook first to see cell indices if needed.9735c27a5a00
overwrite_cell_sourceReplace the entire source of a cell in the currently activated notebook. Returns a diff showing the changes made. Use this when rewriting a cell completely. For small, targeted changes, prefer edit_cell_source instead — it is safer for partial edits.c305777def90
read_cellRead a cell as readable text entries. Includes metadata and source, plus optional formatted output text rather than raw nbformat objects. 3b4fd3a70864
read_notebookRead a notebook and return index, source content, type, execution count of each cell. Using brief format to get a quick overview of the notebook structure and it's useful for locating specific cells for operations like delete or insert. Using detailed format to get detailed information of the notebook and it's useful for debugging and analysis. It is recommended to use brief format with larger limit to get a overview of the notebook structure, then use detailed format with exact index and limit to get the detailed information of some specific cells. 69beac2d803f
restart_notebookRestart the kernel for a specific notebook.8959550d8f7e
unuse_notebookUnuse from a specific notebook and release its resources.748c8f4fa15a
use_notebookUse a notebook and activate it for following cell operations. All cell operations will be performed on the currently activated notebook. Activate new notebook will deactivate the previously activated notebook. Reactivate previously activated notebook using same notebook_name and notebook_path. Kernel selection follows the notebook's existing context. Pass kernel_id to use a kernel that is already running; use_notebook verifies it is alive and creates a Jupyter session for the notebook when no session exists. Without kernel_id, a sandbox already selected with use_sandbox is reused. If none is selected but the notebook already has a live Jupyter session, use_notebook triggers use_sandbox for that session's kernel and reports that in the reply. With neither, no kernel is created. Pass kernel_id=NEW to start an isolated kernel. 12dc562748c0
prompt:jupyter_cite Like @ or # in Coding IDE or CLI, cite specific cells from specified notebook and insert them into the prompt. daf97fa54941

Зафиксируйте эти инструменты

Зафиксируйте то, что jupyter-mcp-server отдаёт вам сегодня, закоммитьте 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.