# UI Polish (remote · uipolish.com)

React components and design rules your coding agent installs and follows.

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

## Components

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

## Channel facts

- Endpoint: `https://uipolish.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.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-11-21.

- **Endpoint Security**: 63/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 3 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 is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 69/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 476 tokens (~158/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 22/100
  - Stability check failed: schema churn in the 15 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions.
- **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 3 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**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

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

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-uipolish-mcp": {
      "type": "http",
      "url": "https://uipolish.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 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 19 to 22.

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

No change was recorded against any check on this day. Stability & Change Management went from 12 to 15.

### 2026-11-18 (score 64, −3)

- [security regression] Stability: 0.37 → fail
- [security regression] A breaking change shipped without a version bump: still 0.1.0
- [security regression] Tool “get_theme” was removed
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_component” rewrote its description, which is the text the model reads
- [security] Tool “list_components” rewrote its description, which is the text the model reads
- [functional improvement] Schema quality: 190 → 158
- [cosmetic] “get_rules” reworded the description of “topic”

### 2026-11-16 (score 67, +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-14 (score 66, +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-12 (score 65, +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-10 (score 64, +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-08 (score 63, +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.

## MCP tools (3)

### `get_rules` (~110 tokens)

Foundation rules: concrete values for motion, states, typography, spacing, surfaces, focus and anti-patterns. Pass a topic for one file; omit it for the token roles, the finished? checklist and the list of topics.

Input parameters:

- `topic` (string): One of: antipatterns, foundations, motion, spacing, states, surfaces, typography, tokens, checklist, tailwind (setup for Tailwind CSS v4 projects), shadcn (using the components on a shadcn/ui theme).

### `list_components` (~29 tokens)

Every UI Polish component with a one-line summary and version. Those marked agent kit are for AI products.

### `get_component` (~127 tokens)

The code and guide for one component: when and when not to use it, every state, motion specs, accessibility notes, before/after. Includes the components it depends on and the npm packages to install.

Input parameters:

- `name` (string, required): Component name from list_components, e.g. button.
- `stack` (string): Target stack. Only react (CSS modules) for now.
- `tailwind` (boolean): True for a Tailwind CSS v4 project: each CSS module comes inside Tailwind's components layer, so utility classes passed in className override it. Leave out otherwise.

## Diagnostics

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

## Score history

- 2026-11-21: 66
- 2026-11-20: 65
- 2026-11-19: 65
- 2026-11-18: 64
- 2026-11-17: 67
- 2026-11-16: 67
- 2026-11-15: 66
- 2026-11-14: 66
- 2026-11-13: 65
- 2026-11-12: 65
- 2026-11-11: 64
- 2026-11-10: 64
- 2026-11-09: 63
- 2026-11-08: 63
- 2026-11-07: 62
- 2026-11-06: 62

## Common questions

### What is the UI Polish MCP server?

UI Polish is an MCP server listed in the public MCP registry as com.uipolish/mcp. React components and design rules your coding agent installs and follows. This page covers its hosted endpoint (https://uipolish.com/mcp).

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

UI Polish scores 66 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 UI Polish MCP server expose?

UI Polish exposes 3 tools: get_rules, list_components, get_component. Their descriptions and schemas cost roughly 266 tokens of context every time the server is loaded.

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

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

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

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

VerifyMCP ran 12 checks on UI Polish, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about UI Polish: Authorization. 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://uipolish.com/mcp
- Repository: https://github.com/cortez/uipolish
- Website: https://uipolish.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-uipolish-mcp/uipolish.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-uipolish-mcp/uipolish/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-uipolish-mcp/uipolish.json
- HTML version of this page: https://verifymcp.io/servers/com-uipolish-mcp/uipolish
