mcp-registry/garden.stanislav.svelte-llm/svelte-llm-mcp · v0.1.0
As of 2026-10-26 16:55 UTC, the Stanislav Svelte Llm Svelte Llm MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 6 minutes.
An MCP server that provides access to Svelte 5 and SvelteKit documentation
Point your MCP client at this streamable-http endpoint: https://svelte-llm.stanislav.garden/mcp/mcp
2 of 2 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 1 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fgarden.stanislav.svelte-llm%2Fsvelte-llm-mcp/fixes
{
"name": "get_documentation",
"description": "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 n",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"section"
],
"properties": {
"section": {
"anyOf": [
{
"type": "string"
},
{
"type": "array",
"items": {
"type": "string"
}
}
],
"description": "The 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"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "list_sections",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/garden.stanislav.svelte-llm/svelte-llm-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/garden.stanislav.svelte-llm/svelte-llm-mcp"}) over MCP.
get_documentation ~266 tokenslist_sections ~144 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fgarden.stanislav.svelte-llm%2Fsvelte-llm-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fgarden.stanislav.svelte-llm%2Fsvelte-llm-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fgarden.stanislav.svelte-llm%2Fsvelte-llm-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fgarden.stanislav.svelte-llm%2Fsvelte-llm-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fgarden.stanislav.svelte-llm%2Fsvelte-llm-mcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:559aef80d63c2cd1…, first seen 2026-10-25, included at leaf 62883 of 74,248. Version history · verify what your client received.
Compare: most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 16:55 UTC, the Stanislav Svelte Llm Svelte Llm MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 6 minutes.
Stanislav Svelte Llm Svelte Llm MCP server advertises 2 tools, including get_documentation, list_sections.
Point your MCP client at this streamable-http endpoint: https://svelte-llm.stanislav.garden/mcp/mcp
Glimind scanned all 2 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.