dev.svelte/mcp

Est-ce que dev.svelte/mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « dev.svelte/mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 4 outils

• get-documentation≈ 501 tokens

  Retrieves 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • section · ? · requis
    The section name(s) to retrieve. Can search by title (e.g., "$state", "load functions") or file path (e.g., "cli/overview"). Supports single string and array of strings

  Exemple d'appel

  {"name": "get-documentation", "arguments": {"section": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list-sections≈ 629 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list-sections", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• playground-link≈ 526 tokens

  Generates 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.

  Paramètres, retour & exemple (3)

  Paramètres

  • name · string · requis
    The name of the Playground, it should reflect the user task
  • files · object · requis
    An object where all the keys are the filenames (with extensions) and the values are the file content. For example: { 'Component.svelte': '<script>...</script>', 'utils.js': 'export function ...' }. The playground accept multiple files so if are importing from other files just include them all at the root level.
  • tailwind · boolean · requis
    If the code requires Tailwind CSS to work...only send true if it it's using tailwind classes in the code

  Exemple d'appel

  {"name": "playground-link", "arguments": {"name": "texte", "files": {}, "tailwind": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte"}}

• svelte-autofixer≈ 508 tokens

  Given 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 user

  Paramètres, retour & exemple (4)

  Paramètres

  • code · string · requis
  • async · boolean · optionnel
    If true the code is an async component/module and might use await in the markup or top-level awaits in the script tag. If possible check the svelte.config.js/svelte.config.ts to check if the option is enabled otherwise asks the user if they prefer using it or not. You can only use this option if the version is 5.
  • filename · string · optionnel
    The filename of the component if available, it MUST be only the Component name with .svelte or .svelte.ts extension and not the entire path.
  • desired_svelte_version · ? · requis
    The desired svelte version as a full semver string (e.g. "5.16.0", the major MUST be 4 or 5)...you MUST read this from the package.json of the user project (or from the installed node_modules/svelte/package.json) since some suggestions are only enabled for newer versions. If you can't find it use some hint from the wording (if the user asks for runes it wants version 5) and pass only the major. Default to 5 in case of doubt.

  Exemple d'appel

  {"name": "svelte-autofixer", "arguments": {"code": "texte", "desired_svelte_version": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"issues": [], "suggestions": [], "require_another_tool_call_after_fixing": true}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.svelte.dev/mcp