# Echo UI (remote · mcp.echo-ui.com)

A tactile React component library, and the design system that keeps your AI agent on-brand.

- Trust score: 75/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.echo-ui.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-echo-ui-mcp/mcp.md), [page](https://verifymcp.io/servers/com-echo-ui-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.echo-ui.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.5`

## 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-21.

- **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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 58/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2407 tokens (~240/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Echo UI MCP server?

Echo UI is a hosted endpoint at https://mcp.echo-ui.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-echo-ui-mcp 'https://mcp.echo-ui.com/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-echo-ui-mcp": {
      "type": "http",
      "url": "https://mcp.echo-ui.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-11-21 (score 75, +1)

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

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

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

### 2026-11-17 (score 73, +1)

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

### 2026-11-15 (score 72, +1)

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

### 2026-11-13 (score 71, +1)

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

### 2026-11-11 (score 70, +1)

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

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

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

### 2026-11-08 (score 68, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (10)

### `search_components` (~97 tokens)

Search Echo UI components

Find the Echo UI item for a job ("a settings toggle", "confirm a delete") or by name. Leads with the best fit, or says plainly that Echo has nothing for the job yet, then lists every match with its install command. The cheapest way to find out what exists, and the first call before writing Echo code.

Input parameters:

- `query` (string): A job in plain words, or a name. Omit to list everything.

### `get_component` (~99 tokens)

Get an Echo UI component

The full record for one component: description, install command, usage (imports + smallest working snippet), composition (part tree), examples, accessibility, motion & sound, prop table and anti-patterns. It's for before writing code that uses the component: the anti-patterns are the part a model gets wrong from priors.

Input parameters:

- `name` (string, required): Registry name ("echo-hardware-button"), bare name ("hardware-button") or title ("HardwareButton").

### `get_tokens` (~102 tokens)

Get Echo UI tokens

The token families: Layer-3 semantic colour roles (--echo-*), sound names, motion's whole vocabulary — the motion tokens, the spring presets, the morph feels and the CSS duration and ease steps — and the shadow recipes. Any name a component's record lists under Motion is here. Echo components are styled and moved only through these: a hex, a duration or a shadow written by hand, or a token name that isn't here, is off Echo's system.

### `get_examples` (~52 tokens)

Get usage examples

Just the usage examples for one component, without the rest of its record. For when the component is already chosen and only its calling convention is needed.

Input parameters:

- `name` (string, required): Registry name, bare name or title.

### `get_accessibility` (~113 tokens)

Get Echo UI accessibility rules

The accessibility rules a consumer of Echo can still get wrong — names on controls, form errors, announcements, focus and target size — and, with a name, what that component's accessibility was actually tested against. Echo guarantees WCAG 2.2 AA; this is the part the guarantee cannot cover for you. It's for before building a form, a dialog or anything icon-only.

Input parameters:

- `name` (string): A component, for its own tested/untested record. Omit for the rules that apply everywhere.

### `check_code` (~186 tokens)

Check code against Echo

Echo's check on a piece of code you've written or are about to write: colours, spacing, radii, shadows and timing off Echo's scales, raw elements where Echo has the component, props a component doesn't take, controls without a name, markup a keyboard or screen reader can't use, restyling Echo from outside, and the screen rules one file can show. The same rules as `npx echo-ui-cli check`, which runs on a whole project with its own theme; this one uses the default theme. Each finding says the Echo way to fix it.

Input parameters:

- `code` (string, required): The file's contents: TSX, JSX or CSS, up to 200,000 characters.
- `file` (string): Its file name, e.g. "app/settings/page.tsx" or "styles.css", which says what it is. TSX when left out.

### `list_styles` (~116 tokens)

List Echo UI styles

Echo's own styles, the looks Echo publishes, each with its one line and its fingerprint on the seven axes styles are placed on; or, with a name, one of them in full: its settings, rules, refusals, fonts, decisions and the slop police's word. The builder's own styles aren't here: they're in their library or the conversation, and fit_styles weighs them with Echo's.

Input parameters:

- `name` (string): One of Echo's styles, e.g. "echo". Omit to list them all.

### `fit_styles` (~201 tokens)

Rank styles for a product

Style Fit's shortlist: Echo's styles, and the builder's own passed in, measured against where a product sits on the seven axes (warmth, volume, density, formality, era, craft, ornament) and put in order: a style that misses a locked axis last, then least past tolerance first, then nearest. The same arithmetic as `npx echo-ui-cli style fit`. It orders; it doesn't pick.

Input parameters:

- `profile` (string, required): Where the product sits, 1 to 5 on each axis: "W4 V2 D1 F2 E3 C3 O3".
- `tolerance` (string): How far a style may drift on each axis, 0 (locked) to 4: "W1 V1 D1 F0 E2 C1 O1". Left out, every axis may drift a point.
- `yours` (array): The builder's own styles, from their library or this conversation.

### `check_style` (~96 tokens)

Check a style

Whether a style.json is one Echo can apply, as `npx echo-ui-cli style check` says it: what stops it, the device it makes (light or dark), what the theme corrects for AA contrast, what the slop police stops (with the question for the builder) or the builder kept, and the decisions it leaves open.

Input parameters:

- `style` (object, required): The style.json's contents, as a JSON object.

### `wear_style` (~161 tokens)

Wear a style

What a style gives a project: a link that makes the whole Echo site wear its colours, the commands that put it in a project, and, for a project without a terminal, its theme CSS and a DESIGN.md with its rules. One of Echo's styles by name, or the builder's own style.json. A style the slop police stops isn't worn; the answer says what to ask the builder.

Input parameters:

- `files` (boolean): Include the theme CSS and DESIGN.md (the default). False when the builder will run the command in a project, which writes both itself.
- `name` (string): One of Echo's styles, e.g. "echo".
- `style` (object): The builder's own style.json, as a JSON object.

## Diagnostics

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

## Score history

- 2026-11-21: 75
- 2026-11-20: 74
- 2026-11-19: 74
- 2026-11-18: 73
- 2026-11-17: 73
- 2026-11-16: 72
- 2026-11-15: 72
- 2026-11-14: 71
- 2026-11-13: 71
- 2026-11-12: 70
- 2026-11-11: 70
- 2026-11-10: 69
- 2026-11-09: 69
- 2026-11-08: 68
- 2026-11-07: 68

## Common questions

### What is the Echo UI MCP server?

Echo UI is an MCP server listed in the public MCP registry as com.echo-ui/mcp. A tactile React component library, and the design system that keeps your AI agent on-brand. This page covers its hosted endpoint (https://mcp.echo-ui.com/mcp).

### Is the Echo UI MCP server safe to use?

Echo UI 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 Echo UI MCP server expose?

Echo UI exposes 10 tools: search_components, get_component, get_tokens, get_examples, get_accessibility, and 5 more. Their descriptions and schemas cost roughly 1,223 tokens of context every time the server is loaded.

### Does the Echo UI MCP server require authentication?

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

### Is the Echo UI MCP server still maintained?

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

### What did VerifyMCP test on the Echo UI MCP server?

VerifyMCP ran 13 checks on Echo UI, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.echo-ui.com/mcp
- Repository: https://github.com/NourMtir0722/echo-ui
- Website: https://echo-ui.com/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-echo-ui-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-echo-ui-mcp/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-echo-ui-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-echo-ui-mcp/mcp
