DRYL Components
REMOTE · COMPONENTS.DRYL.DEV
Blazor UI library DRYL: find components, read their exact API and tokens, validate Razor markup.
Available components
Last scanned (22 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Developer Tools
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 463 tokens (~115/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
- Server version: 3.13.0 → 3.16.0 functional
- 1 Nov 26 +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.
- 31 Oct 26 0
- Server version: 3.12.1 → 3.13.0 functional
- 30 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 29 Oct 26 72
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://components.dryl.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dryl.dev | CN=YE2,O=Let's Encrypt,C=US | 11 Sept 2026 | 10 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 68b15afad387766c2c37664b7727801e2e6 |
| SANs: *.dryl.dev, dryl.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of components.dryl.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| dryl.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://components.dryl.dev/mcp | Verified | 200 | |
| http (plaintext) | http://components.dryl.dev/mcp | HTTPS enforced | 301 | https://components.dryl.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_component Get a DRYL component's API ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Component name, case-insensitive, with or without the 'Dryl' prefix: 'DrylButton', 'button'. |
| Name | Type | Req | Description |
|---|---|---|---|
| aiAware | boolean | yes | – |
| apiUrl | string | yes | – |
| category | string | yes | – |
| docsUrl | string|null | yes | – |
| enums | array | yes | – |
| example | string|null | yes | – |
| methods | array | yes | – |
| name | string | yes | – |
| parameters | array | yes | – |
| summary | string | yes | – |
| version | string | yes | – |
No examples provided.
get_tokens Get DRYL design tokens ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string|null | – | Optional group name, case-insensitive ('Motion', 'Spacing'). Omit to get every group. |
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | yes | – |
| version | string | yes | – |
No examples provided.
search_components Search DRYL components ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of results, 1–50. Default 10. |
| query | string | yes | 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'). |
| Name | Type | Req | Description |
|---|---|---|---|
| hint | string|null | yes | – |
| results | array | yes | – |
| version | string | yes | – |
No examples provided.
validate_markup Validate DRYL Razor markup ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| razor | string | yes | The Razor markup to check — a component, a page or a fragment; up to 50,000 characters. |
| Name | Type | Req | Description |
|---|---|---|---|
| findings | array | yes | – |
| notChecked | string | yes | – |
| valid | boolean | yes | – |
| version | string | yes | – |
No examples provided.
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.
remote · components.dryl.dev
claude mcp add --transport http dev-dryl-components 'https://components.dryl.dev/mcp'
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.