Polyxd
REMOTE · MCP.POLYXD.COM · 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 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 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 Management10
- Stability observed for 3 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 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 current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
How do I install the Polyxd MCP server?
Polyxd is a hosted endpoint at https://mcp.polyxd.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.
remote · mcp.polyxd.com
claude mcp add --transport http com-polyxd-mcp 'https://mcp.polyxd.com/mcp'
{
"mcpServers": {
"com-polyxd-mcp": {
"url": "https://mcp.polyxd.com/mcp"
}
}
} {
"servers": {
"com-polyxd-mcp": {
"type": "http",
"url": "https://mcp.polyxd.com/mcp"
}
}
} [mcp_servers.com-polyxd-mcp] url = "https://mcp.polyxd.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-polyxd-mcp": {
"type": "remote",
"url": "https://mcp.polyxd.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-polyxd-mcp --url 'https://mcp.polyxd.com/mcp' --transport streamable-http
mcp_servers:
com-polyxd-mcp:
url: "https://mcp.polyxd.com/mcp" {
"McpServers": {
"com-polyxd-mcp": {
"Transport": "http",
"Url": "https://mcp.polyxd.com/mcp"
}
}
} assistant mcp add com-polyxd-mcp -t streamable-http -u 'https://mcp.polyxd.com/mcp'
{
"mcpServers": {
"com-polyxd-mcp": {
"type": "http",
"url": "https://mcp.polyxd.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 30 Sept 26 +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.
- 29 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 28 Sept 26 74
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 1 Oct 2026 · Probed https://mcp.polyxd.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=polyxd.com | CN=WE1,O=Google Trust Services,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a0e759106bfd745813392033fb5b464c |
| SANs: polyxd.com, mcp.polyxd.com, *.mcp.polyxd.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.polyxd.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| polyxd.com. | 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://mcp.polyxd.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.polyxd.com/mcp | HTTPS enforced | 301 | https://mcp.polyxd.com/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 →
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 hosted endpoint (https://mcp.polyxd.com/mcp).
Is the Polyxd MCP server safe to use?
Polyxd 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 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.
Does the Polyxd MCP server require authentication?
No. We connected to Polyxd without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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.