Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

garden.stanislav.svelte-llm/svelte-llm-mcp

REMOTE · SVELTE-LLM.STANISLAV.GARDEN · 2 COMPONENTS · SCANNED SEP 21

An MCP server that provides access to Svelte 5 and SvelteKit documentation

0 this week 74 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security60
Transport & Reachability100
Schema Quality & AI Usability46
  • 7% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 4510 tokens (~23/item across 191 items; 2 tools + 189 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the garden.stanislav.svelte-llm/svelte-llm-mcp server?

garden.stanislav.svelte-llm/svelte-llm-mcp is a hosted endpoint at https://svelte-llm.stanislav.garden/mcp/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · svelte-llm.stanislav.garden

# add to Claude Code
claude mcp add --transport http garden-stanislav-svelte-llm-svelte-llm-mcp 'https://svelte-llm.stanislav.garden/mcp/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "garden-stanislav-svelte-llm-svelte-llm-mcp": {
      "url": "https://svelte-llm.stanislav.garden/mcp/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "garden-stanislav-svelte-llm-svelte-llm-mcp": {
      "type": "http",
      "url": "https://svelte-llm.stanislav.garden/mcp/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.garden-stanislav-svelte-llm-svelte-llm-mcp]
url = "https://svelte-llm.stanislav.garden/mcp/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "garden-stanislav-svelte-llm-svelte-llm-mcp": {
      "type": "remote",
      "url": "https://svelte-llm.stanislav.garden/mcp/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add garden-stanislav-svelte-llm-svelte-llm-mcp --url 'https://svelte-llm.stanislav.garden/mcp/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  garden-stanislav-svelte-llm-svelte-llm-mcp:
    url: "https://svelte-llm.stanislav.garden/mcp/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "garden-stanislav-svelte-llm-svelte-llm-mcp": {
      "Transport": "http",
      "Url": "https://svelte-llm.stanislav.garden/mcp/mcp"
    }
  }
}
# add to Vellum
assistant mcp add garden-stanislav-svelte-llm-svelte-llm-mcp -t streamable-http -u 'https://svelte-llm.stanislav.garden/mcp/mcp'
// mcp.json
{
  "mcpServers": {
    "garden-stanislav-svelte-llm-svelte-llm-mcp": {
      "type": "http",
      "url": "https://svelte-llm.stanislav.garden/mcp/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 24 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Probed https://svelte-llm.stanislav.garden/mcp/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=svelte-llm.stanislav.garden CN=YE1,O=Let's Encrypt,C=US 20 Aug 2026 18 Nov 2026 ECDSA 256 ECDSA-SHA384 6fd4e5be224d4934bc88f8c7ea737b7bb17
SANs: svelte-llm.stanislav.garden
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of svelte-llm.stanislav.garden. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
garden. present 27637 8 Verified
stanislav.garden. present 2371 13 Verified
svelte-llm.stanislav.garden. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://svelte-llm.stanislav.garden/mcp/mcp Verified 200
http (plaintext) http://svelte-llm.stanislav.garden/mcp/mcp HTTPS enforced 302 https://svelte-llm.stanislav.garden/mcp/mcp
MCP tools · 2 exposed · ~262 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_documentation ~178

Retrieves full documentation content for Svelte 5 or SvelteKit sections. Supports flexible search by title (e.g., "$state", "routing") or file path (e.g., "docs/svelte/state.md"). 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.

NameTypeReqDescription
sectionyesThe section name(s) to retrieve. Can search by title (e.g., "$state", "load functions") or file path (e.g., "docs/svelte/state.md"). Supports single string and array of strings

No output schema declared.

No examples provided.

list_sections ~84

Lists all available Svelte 5 and SvelteKit documentation sections in a structured format. Returns sections as a list of "* title: [section_title], path: [file_path]" - you can use either the title or path when querying a specific section via the get_documentation tool. Always run list_sections first for any query related to Svelte development to discover available content.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the garden.stanislav.svelte-llm/svelte-llm-mcp server?

garden.stanislav.svelte-llm/svelte-llm-mcp is listed in the public MCP registry as garden.stanislav.svelte-llm/svelte-llm-mcp. An MCP server that provides access to Svelte 5 and SvelteKit documentation. This page covers its hosted endpoint (https://svelte-llm.stanislav.garden/mcp/mcp).

Is the garden.stanislav.svelte-llm/svelte-llm-mcp server safe to use?

garden.stanislav.svelte-llm/svelte-llm-mcp scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the garden.stanislav.svelte-llm/svelte-llm-mcp server expose?

garden.stanislav.svelte-llm/svelte-llm-mcp exposes 2 tools: list_sections, get_documentation. Their descriptions and schemas cost roughly 262 tokens of context every time the server is loaded.

Does the garden.stanislav.svelte-llm/svelte-llm-mcp server require authentication?

No. We connected to garden.stanislav.svelte-llm/svelte-llm-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the garden.stanislav.svelte-llm/svelte-llm-mcp server still maintained?

garden.stanislav.svelte-llm/svelte-llm-mcp is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.