Polyxd
NPM · @POLYXD/MCP · 2 COMPONENTS · SCANNED OCT 1
Write Polyxd UI documents, check them, and show them as real screens in any design-system pack.
Available components
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 8 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to visualfart/polyxd). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability89
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1689 tokens (~44/item across 38 items; 6 tools + 32 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
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.
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.
npm · @polyxd/mcp
claude mcp add com-polyxd-mcp -- npx -y @polyxd/mcp
{
"mcpServers": {
"com-polyxd-mcp": {
"command": "npx",
"args": [
"-y",
"@polyxd/mcp"
]
}
}
} {
"servers": {
"com-polyxd-mcp": {
"command": "npx",
"args": [
"-y",
"@polyxd/mcp"
]
}
}
} codex mcp add com-polyxd-mcp -- npx -y @polyxd/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-polyxd-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@polyxd/mcp"
],
"enabled": true
}
}
} openclaw mcp add com-polyxd-mcp --command npx --arg -y --arg @polyxd/mcp
mcp_servers:
com-polyxd-mcp:
command: "npx"
args: ["-y", "@polyxd/mcp"] {
"McpServers": {
"com-polyxd-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@polyxd/mcp"
]
}
}
} assistant mcp add com-polyxd-mcp -t stdio -c npx -a -y @polyxd/mcp
{
"mcpServers": {
"com-polyxd-mcp": {
"command": "npx",
"args": [
"-y",
"@polyxd/mcp"
]
}
}
} 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.
- 29 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Sept 26 68
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 30 Sept 2026 · Analysed npm/@polyxd/mcp@0.4.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | visualfart/polyxd |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/visualfart/polyxd/.github/workflows/release.yml@refs/tags/v0.4.1 |
| Rekor log index | 2988107700 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:c7dfd4b66ffdaba65ba0fd80e3d1877f2a8067b83a7870b3e91bef2a7f3454d88bc032e0faaa5100e69abb5c15e04cff5d313fd6436c39a28a8e95d66 |
Background: How many MCP packages publish verified provenance →
Dependencies 8 packages
| Packages resolved | 8 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
polyxd_components List Polyxd components ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | A component name, e.g. "Choice", for its full definition. |
| Name | Type | Req | Description |
|---|---|---|---|
| component | object | – | One component's full definition. |
| components | array | – | Every component, in the spec's order. |
No examples provided.
polyxd_guide Polyxd guide ~54
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| guide | string | yes | 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 | yes | The version of the Polyxd spec this server implements, e.g. "0.3.0". Documents set it as their "specVersion". |
No examples provided.
polyxd_packs List Polyxd packs ~52
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| default | string | yes | The pack polyxd_show uses when none is given. |
| packs | array | yes | Every pack, for polyxd_show's "pack" argument. |
No examples provided.
polyxd_show Show a Polyxd screen ~354
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.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | The values the screen shows, bound by {"path": "/pointer"}. Replaces the document's own "data" when given. |
| document | object | yes | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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". |
No examples provided.
polyxd_validate Validate a Polyxd document ~145
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.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | The values the screen shows, bound by {"path": "/pointer"}. Replaces the document's own "data" when given. |
| document | object | yes | A Polyxd UI document: {specVersion, surface, root, components, data?}. polyxd_guide explains the format. |
| Name | Type | Req | Description |
|---|---|---|---|
| errors | integer | yes | How many errors. Fix every one before showing the document. |
| issues | array | yes | Every error and warning, each at its JSON Pointer with a hint. Empty when the document is clean. |
| valid | boolean | yes | True when the document has no errors and can be shown. Warnings do not make it invalid. |
| warnings | integer | yes | How many warnings. Advice; they do not stop the document being shown. |
No examples provided.
polyxd_verify Verify a Polyxd document ~206
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | The name of the Design Direction the document was held to, when one was given and it has a name. |
| errors | integer | yes | How many errors. Fix every one before showing the document. |
| findings | array | yes | Every check that failed. Empty when the document passes with no warnings. |
| rules | integer | yes | How many Design Direction rules were checked. 0 without a direction. |
| warnings | integer | yes | How many warnings. Advice; they do not stop the document being shown. |
No examples provided.
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 30 September 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 30 September 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.