# Polyxd (npm · @polyxd/mcp)

Write Polyxd UI documents, check them, and show them as real screens in any design-system pack.

- Trust score: 83/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-01

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@polyxd/mcp`
- Version: `0.4.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-10-01.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 0 of 8 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to visualfart/polyxd).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 89/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1689 tokens (~44/item across 38 items; 6 tools + 32 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 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.
  - Supports UI / widget rendering.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

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

Polyxd runs locally as an npm package, launched with npx -y @polyxd/mcp. 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 com-polyxd-mcp -- npx -y @polyxd/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-polyxd-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@polyxd/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-polyxd-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@polyxd/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-polyxd-mcp -- npx -y @polyxd/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-polyxd-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@polyxd/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-polyxd-mcp --command npx --arg -y --arg @polyxd/mcp
```

### Hermes

```yaml
mcp_servers:
  com-polyxd-mcp:
    command: "npx"
    args: ["-y", "@polyxd/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-polyxd-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@polyxd/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-polyxd-mcp -t stdio -c npx -a -y @polyxd/mcp
```

### Other

```json
{
  "mcpServers": {
    "com-polyxd-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@polyxd/mcp"
      ]
    }
  }
}
```

## 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-29 (score 83, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-28 (score 68)

First indexed and scored.

## MCP tools (6)

### `polyxd_guide` (~54 tokens)

Polyxd guide

Returns the instructions for writing a Polyxd UI document: the document shape, the rules for generated screens, bindings, actions, every component with its props, and the patterns. Call this once before writing your first document.

Output parameters:

- `guide` (string): The instructions for writing a Polyxd UI document: how to use these tools, the document shape, the rules, bindings, actions, every component with its props, and the patterns. The same text as the res…
- `specVersion` (string): The version of the Polyxd spec this server implements, e.g. "0.3.0". Documents set it as their "specVersion".

### `polyxd_validate` (~145 tokens)

Validate a Polyxd document

Checks a Polyxd UI document against the spec: the schema, ids and references, bindings against the data, actions, and the rules for generated screens. Returns every issue with its JSON Pointer, the component it is in, and a hint saying what to change. Call it after writing or changing a document, and fix every error before showing it.

Input parameters:

- `data` (object): The values the screen shows, bound by {"path": "/pointer"}. Replaces the document's own "data" when given.
- `document` (object, required): A Polyxd UI document: {specVersion, surface, root, components, data?}. polyxd_guide explains the format.

Output parameters:

- `errors` (integer): How many errors. Fix every one before showing the document.
- `issues` (array): Every error and warning, each at its JSON Pointer with a hint. Empty when the document is clean.
- `valid` (boolean): True when the document has no errors and can be shown. Warnings do not make it invalid.
- `warnings` (integer): How many warnings. Advice; they do not stop the document being shown.

### `polyxd_verify` (~206 tokens)

Verify a Polyxd document

Runs the Polyxd verifier's document checks: the spec validator, the pattern the surface declares, readable and distinct labels, one primary action per view, at most six inputs per view, entity-first flows, confirmations, and, when you pass one, a Design Direction's rules and voice. Returns a compact report. Example directions by name: calm-finance, playful-personal.

Input parameters:

- `data` (object): The values the screen shows, bound by {"path": "/pointer"}. Replaces the document's own "data" when given.
- `direction`: A Design Direction to hold the document to: the direction object, or the name of an example direction.
- `document` (object, required): A Polyxd UI document: {specVersion, surface, root, components, data?}. polyxd_guide explains the format.
- `registry` (object): A capability registry ({capabilities: [...]}) to check the document's actions against. Leave out when there is none.

Output parameters:

- `direction` (string): The name of the Design Direction the document was held to, when one was given and it has a name.
- `errors` (integer): How many errors. Fix every one before showing the document.
- `findings` (array): Every check that failed. Empty when the document passes with no warnings.
- `rules` (integer): How many Design Direction rules were checked. 0 without a direction.
- `warnings` (integer): How many warnings. Advice; they do not stop the document being shown.

### `polyxd_show` (~354 tokens)

Show a Polyxd screen

Validates a Polyxd UI document and shows it to the user as an interactive screen, drawn by the Polyxd renderer in the design-system pack you choose (default material3). Shows nothing if the document has errors; fix them first with polyxd_validate. When the user presses an action in the screen, you receive a chat message from the user naming the action and its context; that only tells you their choice, and nothing has been submitted or paid. Packs: material3, antd, bootstrap, carbon, chakra, fluent, govuk, mantine, polaris, primer, radix, shadcn, spectrum, brutalist, civic, editorial, finance, glass, health, mono, neon, pastel, sketch, terminal, wireframe.

Input parameters:

- `data` (object): The values the screen shows, bound by {"path": "/pointer"}. Replaces the document's own "data" when given.
- `document` (object, required): A Polyxd UI document: {specVersion, surface, root, components, data?}. polyxd_guide explains the format.
- `mode` (string): Light or dark. Leave out to follow the host's theme.
- `pack` (string): The design-system pack to draw the screen in, by id: material3, antd, bootstrap, carbon, chakra, fluent, govuk, mantine, polaris, primer, radix, shadcn, spectrum, brutalist, civic, editorial, finance…

Output parameters:

- `document` (object): The Polyxd UI document as shown, with the separately passed data merged in as its "data". The MCP App renders it.
- `issues` (array): When not shown: the document's errors and warnings, each at its JSON Pointer with a hint.
- `mode` (string): Light or dark, when one was asked for. Absent: the screen follows the host's theme.
- `pack` (string): The design-system pack the screen is drawn in.
- `packName` (string): The pack's display name, e.g. "Material 3".
- `shown` (boolean): Whether the screen was shown to the user. False when the document has errors.
- `specVersion` (string): The version of the Polyxd spec this server implements, e.g. "0.3.0". Documents set it as their "specVersion".

### `polyxd_packs` (~52 tokens)

List Polyxd packs

Lists the design-system packs polyxd_show can draw a screen in: published design systems (Material 3, Carbon, GOV.UK and others) and original templates. The same document looks native in each.

Output parameters:

- `default` (string): The pack polyxd_show uses when none is given.
- `packs` (array): Every pack, for polyxd_show's "pack" argument.

### `polyxd_components` (~83 tokens)

List Polyxd components

Lists the semantic components a Polyxd document can use, with a one-line summary each. Pass "name" for one component's full definition: every prop and its type, which are required, when to use it and when not to, and how it renders.

Input parameters:

- `name` (string): A component name, e.g. "Choice", for its full definition.

Output parameters:

- `component` (object): One component's full definition.
- `components` (array): Every component, in the spec's order.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-polyxd-mcp/polyxd-mcp#diagnostics

## Score history

- 2026-10-01: 83
- 2026-09-30: 83
- 2026-09-29: 83
- 2026-09-28: 68

## Common questions

### What is the Polyxd MCP server?

Polyxd is an MCP server listed in the public MCP registry as com.polyxd/mcp. Write Polyxd UI documents, check them, and show them as real screens in any design-system pack. This page covers its npm package (@polyxd/mcp).

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

Polyxd scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 1 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Polyxd MCP server expose?

Polyxd exposes 6 tools: polyxd_guide, polyxd_validate, polyxd_verify, polyxd_show, polyxd_packs, polyxd_components. Their descriptions and schemas cost roughly 894 tokens of context every time the server is loaded.

### Is the Polyxd MCP server still maintained?

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

### What licence is the Polyxd MCP server under?

Polyxd declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@polyxd/mcp
- Socket report: https://socket.dev/npm/package/@polyxd/mcp
- Repository: https://github.com/visualfart/polyxd
- Website: https://polyxd.com/docs/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/com-polyxd-mcp/polyxd-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-polyxd-mcp/polyxd-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-polyxd-mcp/polyxd-mcp