Verfy

MCP-серверы / @sveltejs/mcp

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

@sveltejs/mcp

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

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

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

0.1.29 → 0.1.30

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

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

0.1.28 → 0.1.29

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

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

0.1.27 → 0.1.28

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

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

0.1.26 → 0.1.27

выпуск patch, 19 октября 2026 г.
list-sections: изменено: описание
До (0.1.26)
Lists all available Svelte 5 and SvelteKit documentation sections in a structured format. Each section includes a "use_cases" field that describes WHEN this documentation would be useful. You should carefully analyze the use_cases field to determine which sections are relevant for the user's query. The use_cases contain comma-separated keywords describing project types (e.g., "e-commerce", "blog"), features (e.g., "authentication", "forms"), components (e.g., "slider", "modal"), development stages (e.g., "deployment", "testing"), or "always" for fundamental concepts. Match these use_cases against the user's intent - for example, if building an e-commerce site, fetch sections with use_cases containing "e-commerce", "product listings", "shopping cart", etc. If building a slider, look for "slider", "carousel", "animation", etc. Returns sections as "* title: [section_title], use_cases: [use_cases], path: [file_path]". Always run list-sections FIRST for any Svelte query, then analyze ALL use_cases to identify relevant sections, and finally use get_documentation to fetch ALL relevant sections at once.
После (0.1.27)
Lists all available Svelte 5 and SvelteKit documentation sections in a structured format. Each section includes a "use_cases" field that describes WHEN this documentation would be useful. You should carefully analyze the use_cases field to determine which sections are relevant for the user's query. The use_cases contain comma-separated keywords describing project types (e.g., "e-commerce", "blog"), features (e.g., "authentication", "forms"), components (e.g., "slider", "modal"), development stages (e.g., "deployment", "testing"), or "always" for fundamental concepts. Match these use_cases against the user's intent - for example, if building an e-commerce site, fetch sections with use_cases containing "e-commerce", "product listings", "shopping cart", etc. If building a slider, look for "slider", "carousel", "animation", etc. Returns sections as "* title: [section_title], use_cases: [use_cases], path: [file_path]". Always run list-sections FIRST for any Svelte query, then analyze ALL use_cases to identify relevant sections, and finally use get-documentation to fetch ALL relevant sections at once.

svelte-autofixer: изменено: схема входных данных

0.1.25 → 0.1.26

выпуск patch, 7 августа 2026 г.

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

Проверенные выпуски: 0.1.25 (2026-06-26); 0.1.26 (2026-08-07); 0.1.27 (2026-10-19); 0.1.28 (2026-10-26); 0.1.29 (2026-11-03); 0.1.30 (2026-11-04).

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

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

Инструменты в 0.1.30
ИнструментОписаниеОтпечаток
get-documentationRetrieves full documentation content for Svelte 5 or SvelteKit sections. Supports flexible search by title (e.g., "$state", "routing") or file path (e.g., "cli/overview"). Can accept a single section name or an array of sections. Before running this, make sure to analyze the users query, as well as the output from list-sections (which should be called first). Then ask for ALL relevant sections the user might require. For example, if the user asks to build anything interactive, you will need to fetch all relevant runes, and so on. Before calling this tool, try to implement Svelte components using your own knowledge and the `svelte-autofixer` tool, since calling this tool is token intensive.92a45dfd10e2
list-sectionsLists all available Svelte 5 and SvelteKit documentation sections in a structured format. Each section includes a "use_cases" field that describes WHEN this documentation would be useful. You should carefully analyze the use_cases field to determine which sections are relevant for the user's query. The use_cases contain comma-separated keywords describing project types (e.g., "e-commerce", "blog"), features (e.g., "authentication", "forms"), components (e.g., "slider", "modal"), development stages (e.g., "deployment", "testing"), or "always" for fundamental concepts. Match these use_cases against the user's intent - for example, if building an e-commerce site, fetch sections with use_cases containing "e-commerce", "product listings", "shopping cart", etc. If building a slider, look for "slider", "carousel", "animation", etc. Returns sections as "* title: [section_title], use_cases: [use_cases], path: [file_path]". Always run list-sections FIRST for any Svelte query, then analyze ALL use_cases to identify relevant sections, and finally use get-documentation to fetch ALL relevant sections at once.1565e842c210
playground-linkGenerates a Playground link given a Svelte code snippet. Once you have the final version of the code you want to send to the user, ALWAYS ask the user if it wants a playground link to allow it to quickly check the code in the playground before calling this tool. NEVER use this tool if you have written the component to a file in the user project. The playground accept multiple files so if are importing from other files just include them all at the root level.abf9e952ac3e
svelte-autofixerGiven a svelte component or module returns a list of suggestions to fix any issues it has. This tool MUST be used whenever the user is asking to write svelte code before sending the code back to the usera2cc4054a792
prompt:svelte-taskUse this Prompt to ask for any svelte related task. It will automatically instruct the LLM on how to best use the autofixer and how to query for documentation pages.a8014ba5dd85

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

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