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

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

- name: garden.stanislav.svelte-llm/svelte-llm-mcp
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 78/100
- quality: 79/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/garden.stanislav.svelte-llm%2Fsvelte-llm-mcp
- tools: https://api.protogrid.dev/v1/servers/garden.stanislav.svelte-llm%2Fsvelte-llm-mcp/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "svelte-llm-mcp": {
      "type": "http",
      "url": "https://svelte-llm.stanislav.garden/mcp/mcp"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 100
- freshness: 25
- provenance: 75
- drivers: +repository +dns-namespace +reachable +uptime-100% -stale-404d
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 79/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 71 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: get_documentation (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_sections (readOnlyHint, destructiveHint, idempotentHint, openWorldHint)
- pass `tools.token_cost`: about 365 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 2, about 365 tokens to load them all
- tool set hash: e4eb8ac9625b5b015a6377ad2e26c5d2
- badge: [![protogrid quality](https://protogrid.dev/badge/garden.stanislav.svelte-llm/svelte-llm-mcp.svg)](https://protogrid.dev/servers/garden.stanislav.svelte-llm/svelte-llm-mcp)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://svelte-llm.stanislav.garden/mcp/mcp (streamable-http, auth none, reachable true, uptime30d 1)
- https://svelte-llm.stanislav.garden/mcp/sse (sse, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (2)

- `get_documentation`: 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.
- `list_sections`: 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.