Svelte MCP server
4 tools · Last check that passed 27 Oct 2026, 01:50 UTC
The Svelte team's own remote MCP server gives an agent the Svelte 5 and SvelteKit documentation, a checker for Svelte code and playground links, with no sign-in. Once a day, Stackduke connects to it the way any MCP client would, with no account and no sign-in, and lists its tools. It never runs them.
All 4 tools
| Tool | Counted as |
|---|---|
get-documentation | Said to only read |
list-sections | Said to only read |
playground-link | Said to only read |
svelte-autofixer | Said to only read |
The tools the server listed at the last check that passed, at its default address and settings, with no sign-in; an account that signs in, or other settings, may see other tools. What a tool is counted as doing is Stackduke's cautious reading of the server's labels, the tool's name and its description: where they disagree it takes whichever says the tool can do most, so it overcounts on purpose. It does not say the server is safe, and it does not list what a tool cannot do. Descriptions are not shown, because they are written for models and may try to steer them.
Recent checks
12 of the last 12 checks passed
A check passes when the server lists its tools. Checked at https://mcp.svelte.dev/mcp.
Recent changes
20 Oct 2026, 09:43 UTC, after a check on 19 Oct 2026, 10:08 UTC
Description rewritten on list-sections. Title changed on list-sections.
From the scan of 27 Oct 2026, 01:52 UTC. "Changed" and "Can do more" count changes from the last 30 days; older ones stay listed here. A change made and undone between two checks is not seen. Every check is in the scanner's public data.
Know when Svelte's tools change.
One email when Svelte's official MCP server adds, removes or changes tools, with what changed. Nothing else.
What to watch for
- Code the agent checks with svelte-autofixer goes to the remote server. Svelte says its team does not log, store or inspect it. Svelte's remote MCP setup
- Its playground-link tool stores the code only in the link it returns, so the code goes wherever the link goes. Svelte's MCP tools documentation
- Documentation comes back to the agent as text, and text an agent reads can carry instructions for it. OWASP, prompt injection
How to limit it
With Svelte's own settings, as its documentation describes them. Stackduke has not tested them.
- Svelte also publishes the server as a local package, @sveltejs/mcp. We recommend it for code that should not leave the machine. Svelte's local MCP setup
What Stackduke is designed to do
Stackduke is designed to sit between your agents and their MCP servers: to check each tool call against your rules before it runs, hold the risky ones for a person to approve, and keep a record of what was decided.
It does not yet forward or block tool calls for customers. Today it reads what this server offers and publishes what changes.