# SvGrid (remote · mcp.svgrid.com)

Checks AI-written SvGrid code against the real API, plus version-pinned Svelte 5 grid docs.

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-27

## Components

- remote · `mcp.svgrid.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-svgrid-svgrid/mcp.md), [page](https://verifymcp.io/servers/com-svgrid-svgrid/mcp)
- npm · `@svgrid/mcp`: 72/100, [markdown](https://verifymcp.io/servers/com-svgrid-svgrid/svgrid-mcp.md), [page](https://verifymcp.io/servers/com-svgrid-svgrid/svgrid-mcp)

## Channel facts

- Endpoint: `https://mcp.svgrid.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `3.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-27.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 83/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 544 tokens (~90/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the SvGrid MCP server?

SvGrid is a hosted endpoint at https://mcp.svgrid.com/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.

### Claude

```bash
claude mcp add --transport http com-svgrid-svgrid 'https://mcp.svgrid.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-svgrid-svgrid": {
      "url": "https://mcp.svgrid.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-svgrid-svgrid": {
      "type": "http",
      "url": "https://mcp.svgrid.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-svgrid-svgrid]
url = "https://mcp.svgrid.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-svgrid-svgrid": {
      "type": "remote",
      "url": "https://mcp.svgrid.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-svgrid-svgrid --url 'https://mcp.svgrid.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-svgrid-svgrid:
    url: "https://mcp.svgrid.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-svgrid-svgrid": {
      "Transport": "http",
      "Url": "https://mcp.svgrid.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-svgrid-svgrid -t streamable-http -u 'https://mcp.svgrid.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-svgrid-svgrid": {
      "type": "http",
      "url": "https://mcp.svgrid.com/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-27 (score 72, +1)

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

### 2026-09-25 (score 71, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 71, +1)

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

### 2026-09-22 (score 70, +1)

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

### 2026-09-20 (score 69, +1)

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

### 2026-09-18 (score 68, +1)

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

### 2026-09-16 (score 67, +1)

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

### 2026-09-14 (score 66, +1)

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

## MCP tools (6)

### `search` (~93 tokens)

Ranked full-text search across the SvGrid documentation and demo catalogue. Returns the best pages first with an excerpt and an id you pass to `fetch`. Use this before writing SvGrid code so the API names come from the docs rather than from memory.

Input parameters:

- `limit` (number): Max results, default 10, max 25.
- `query` (string, required): What you are looking for, e.g. "row virtualization".

### `fetch` (~63 tokens)

Return the full text behind a search result. Pass a doc slug ("help/columns/column-definitions") or a demo id prefixed with "demo:" ("demo:11-stock-market").

Input parameters:

- `id` (string, required): A doc slug, or "demo:<id>".

### `list_examples` (~106 tokens)

Browse the SvGrid demo catalogue: id, title, category and a one-line blurb. Call with no arguments for the category index, then filter with `query` or `category`, then read one with get_example_source.

Input parameters:

- `category` (string): Exact category, e.g. "Kanban".
- `limit` (number): Max results, default 25, max 100.
- `query` (string): Free-text filter over id, title, blurb and category.

### `get_example_source` (~59 tokens)

Return the full .svelte source of one demo by id (e.g. "11-stock-market") - working code to copy, not a summary of it.

Input parameters:

- `id` (string, required): Demo id, e.g. "11-stock-market".

### `get_api_reference` (~48 tokens)

The SvGrid public API grouped by category (components, headless, scheduler, data ops, export, row models, features, virtualization, accessibility, utilities), for the version this server tracks.

### `check_svgrid_code` (~136 tokens)

Verify SvGrid code BEFORE handing it to the user. Checks the source against the real exported surface of the current version - <SvGrid> prop names, ColumnDef keys, grid API methods, importable symbols and theme files - plus Svelte 5 runes rules, and returns line-numbered diagnostics with the exact replacement for each. Run it on every file you write that uses SvGrid, fix what it reports, and run it again.

Input parameters:

- `filename` (string): File name, used to pick which rules apply. Defaults to "Component.svelte".
- `source` (string, required): The full file contents to check.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-svgrid-svgrid/mcp#diagnostics

## Score history

- 2026-09-27: 72
- 2026-09-26: 71
- 2026-09-25: 71
- 2026-09-24: 71
- 2026-09-23: 70
- 2026-09-22: 70
- 2026-09-21: 69
- 2026-09-20: 69
- 2026-09-19: 68
- 2026-09-18: 68
- 2026-09-17: 67
- 2026-09-16: 67
- 2026-09-15: 66
- 2026-09-14: 66
- 2026-09-13: 65
- 2026-09-12: 65
- 2026-09-11: 64
- 2026-09-10: 64
- 2026-09-09: 64
- 2026-09-08: 63
- 2026-09-07: 63
- 2026-09-06: 62
- 2026-09-05: 62
- 2026-09-04: 61
- 2026-09-03: 61
- 2026-09-02: 60
- 2026-09-01: 60

## Common questions

### What is the SvGrid MCP server?

SvGrid is an MCP server listed in the public MCP registry as com.svgrid/svgrid. Checks AI-written SvGrid code against the real API, plus version-pinned Svelte 5 grid docs. This page covers its hosted endpoint (https://mcp.svgrid.com/mcp).

### Is the SvGrid MCP server safe to use?

SvGrid scores 72 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 SvGrid MCP server expose?

SvGrid exposes 6 tools: search, fetch, list_examples, get_example_source, get_api_reference, check_svgrid_code. Their descriptions and schemas cost roughly 505 tokens of context every time the server is loaded.

### Does the SvGrid MCP server require authentication?

No. We connected to SvGrid without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SvGrid MCP server still maintained?

SvGrid is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.svgrid.com/mcp
- Repository: https://github.com/sv-grid/sv-grid
- Website: https://svgrid.com/docs/help/mcp-server/
- Changelog RSS feed: https://verifymcp.io/servers/com-svgrid-svgrid/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-svgrid-svgrid/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-svgrid-svgrid/mcp