Remote MCP · Endpoint

Svelte MCP MCP server

No. Svelte MCP answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.svelte.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.svelte/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
854 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
The official Svelte MCP server providing docs and autofixing tools for Svelte development
Listing
From the official MCP registry (active).
Recent checks of Svelte MCP
CheckedResultHandshake
1 hour agoHandshake completed854 ms
2 days agoHandshake completed45 ms
4 days agoHandshake completed69 ms
5 days agoHandshake completed34 ms
7 days agoHandshake completed40 ms
8 days agoHandshake completed48 ms
9 days agoHandshake completed61 ms
12 days agoHandshake completed34 ms
13 days agoHandshake completed53 ms
15 days agoHandshake completed162 ms
16 days agoHandshake completed66 ms
18 days agoHandshake completed45 ms
19 days agoHandshake completed35 ms
20 days agoHandshake completed42 ms
20 days agoHandshake completed46 ms
21 days agoHandshake completed34 ms
22 days agoHandshake completed222 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Svelte MCP and makes no claim about it beyond what these checks measured.