# DRYL Components (remote · components.dryl.dev)

Blazor UI library DRYL: find components, read their exact API and tokens, validate Razor markup.

- Trust score: 75/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `components.dryl.dev`: 75/100 (this document), [markdown](https://verifymcp.io/servers/dev-dryl-components/components.md), [page](https://verifymcp.io/servers/dev-dryl-components/components)

## Channel facts

- Endpoint: `https://components.dryl.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `3.12.0`

## 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-11-04.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 82/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 463 tokens (~115/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the DRYL Components MCP server?

DRYL Components is a hosted endpoint at https://components.dryl.dev/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 dev-dryl-components 'https://components.dryl.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-dryl-components": {
      "url": "https://components.dryl.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-dryl-components": {
      "type": "http",
      "url": "https://components.dryl.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-dryl-components]
url = "https://components.dryl.dev/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add dev-dryl-components --url 'https://components.dryl.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-dryl-components:
    url: "https://components.dryl.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-dryl-components": {
      "Transport": "http",
      "Url": "https://components.dryl.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-dryl-components -t streamable-http -u 'https://components.dryl.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-dryl-components": {
      "type": "http",
      "url": "https://components.dryl.dev/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-11-03 (score 75, +1)

- [functional] Server version: 3.13.0 → 3.16.0

### 2026-11-01 (score 74, +1)

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

### 2026-10-31 (score 73, 0)

- [functional] Server version: 3.12.1 → 3.13.0

### 2026-10-30 (score 73, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-29 (score 72)

First indexed and scored.

## MCP tools (4)

### `search_components` (~127 tokens)

Search DRYL components

Find DRYL Blazor components (DRYL.Components and DRYL.Components.Agents) by name, title, category or purpose. Use this first when you need a component for a job; then call get_component for its exact API.

Input parameters:

- `limit` (integer): Maximum number of results, 1–50. Default 10.
- `query` (string, required): What to look for: a component name with or without the 'Dryl' prefix ('button', 'DrylDatePicker'), a category ('Inputs') or a purpose ('date', 'chart', 'streaming text').

Output parameters:

- `hint` (string|null)
- `results` (array)
- `version` (string)

### `get_component` (~124 tokens)

Get a DRYL component's API

The exact public API of one DRYL component: every parameter with type, default and description, the members of every enum it uses, its public methods and a canonical Razor example. DRYL variants are enums, never strings: write an enum value as qualifiedName.Member (e.g. Variant="DrylButton.ButtonVariant.Secondary") — many enums are nested in their component, so the bare enum name does not compile.

Input parameters:

- `name` (string, required): Component name, case-insensitive, with or without the 'Dryl' prefix: 'DrylButton', 'button'.

Output parameters:

- `aiAware` (boolean)
- `apiUrl` (string)
- `category` (string)
- `docsUrl` (string|null)
- `enums` (array)
- `example` (string|null)
- `methods` (array)
- `name` (string)
- `parameters` (array)
- `summary` (string)
- `version` (string)

### `get_tokens` (~106 tokens)

Get DRYL design tokens

The CSS custom properties DRYL styles itself with, grouped (colors, glass, accent, spacing, radius, motion, …), with the dark value and — where light mode differs — the light value. Reference these with var(--name) in your CSS instead of writing literal colors, sizes or durations; DRYL follows the user's color mode through them.

Input parameters:

- `category` (string|null): Optional group name, case-insensitive ('Motion', 'Spacing'). Omit to get every group.

Output parameters:

- `categories` (array)
- `version` (string)

### `validate_markup` (~106 tokens)

Validate DRYL Razor markup

Check a Razor snippet's <Dryl…> tags against DRYL's real API before you finish: unknown components, unknown parameters, and enum parameters given a string or a member that does not exist — each with a suggested fix. Call it on every DRYL markup you write or change. It scans tags; it does not compile Razor.

Input parameters:

- `razor` (string, required): The Razor markup to check — a component, a page or a fragment; up to 50,000 characters.

Output parameters:

- `findings` (array)
- `notChecked` (string)
- `valid` (boolean)
- `version` (string)

## Diagnostics

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

## Score history

- 2026-11-04: 75
- 2026-11-03: 75
- 2026-11-02: 74
- 2026-11-01: 74
- 2026-10-31: 73
- 2026-10-30: 73
- 2026-10-29: 72

## Common questions

### What is the DRYL Components MCP server?

DRYL Components is an MCP server listed in the public MCP registry as dev.dryl/components. Blazor UI library DRYL: find components, read their exact API and tokens, validate Razor markup. This page covers its hosted endpoint (https://components.dryl.dev/mcp).

### Is the DRYL Components MCP server safe to use?

DRYL Components scores 75 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 DRYL Components MCP server expose?

DRYL Components exposes 4 tools: search_components, get_component, get_tokens, validate_markup. Their descriptions and schemas cost roughly 463 tokens of context every time the server is loaded.

### Does the DRYL Components MCP server require authentication?

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

### Is the DRYL Components MCP server still maintained?

DRYL Components is still listed as active in the MCP registry. We last reached this channel on 4 November 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://components.dryl.dev/mcp
- Repository: https://github.com/Zimpi/DRYL.Website
- Website: https://components.dryl.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-dryl-components/components.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-dryl-components/components.json
- HTML version of this page: https://verifymcp.io/servers/dev-dryl-components/components