Polyxd MCP server

• Registry namecom.polyxd/mcpverified in the MCP registry

The registry name sits under polyxd.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-27
• Tools7
• Server calls itselfpolyxd
• Server version0.4.6
• Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 64 ms.

• Its tools do every use case we checked: draw a refund screen in a chosen design system; check generated screens before anyone sees them.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP score92 of 100answers 100 · does the job 100 · definitions 100 · context 100 · use 19 · connects 100
• What an agent can do with it2 of 2 use cases
• Use5 GitHub stars
• Answered100% of days7 of 7 daily checks
• Median first answer195 ms
• Space in an agent's context≈ 1,390 tokensthe definitions of all its tools (7), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results7 of 7 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• 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.

• polyxd_validate

  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…

• polyxd_verify

  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…

• polyxd_show

  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_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.

• 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.

• polyxd_docs

  Searches the polyxd.com docs, as of this server's version: installing and using the React and Web Components renderers, the spec, the verifier and its CLI, the runtime, the generation server, design systems and packs, Design Directions…