Kite vs UX Pilot MCP server

Kite 78

Closed service with a dated changelog. The latest entry is 1 November 2026 (30). 15 dated entries between 6 October and 1 November 2026, including Pro on 18 October, Windows, shaders and website design systems on 23 October and the agent page, version, comment and export tools on 25 October (20). Support is hello@kite.new, a Support link in the docs, 'your feedback first in line' on Pro and dedicated support on Team; no community channel, forum or issue tracker, and the plugin repository has no issues (8 of 15). new.kite/kite 1.0.0 is in the official MCP registry under a DNS-verified namespace since 21 October 2026 (15). No packages to judge; the MIT plugin repository was pushed once on 7 October 2026 and the desktop apps update themselves (5 of 10). 30+20+8+15+5 = 78.

UX Pilot MCP server 45

Registry 3.0.0 and repository on 4 November 2026 (30). Dated releases not found (0). Issues not read (0). Official registry entry ai.uxpilot/uxpilot (15). README-only repository (0). 30 + 0 + 0 + 15 + 0 = 45. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.

Kite 44

Closed service. The terms of use (8 September 2026) run to about 200 words on content, prohibited use, links, availability and changes and name no legal entity, address or governing law, so the contracting party is unknown (8 of 30). The privacy policy (14 October 2026) names eight services, says files are not read, trained on or sold, discloses masked session replays and error replays, gives the agent token's 7-day life renewable to 90 days (matching auth.md and the integration page), the 30-day purge of deleted pages and the one-month deletion of a closed account's files, and the Figma token's handling; no DPA and no retention period for logs beyond the providers' own (20 of 30). No deprecation policy or dated notices; the terms promise email or in-app notice of changes that matter and the changelog dates additions, not removals (4 of 20). Telemetry (PostHog, Sentry) is disclosed with what it excludes and no opt-out beyond product-news emails; service locations are given only for PostHog and Sentry (US) (10 of 20). 8+20+4+10 = 42.

UX Pilot MCP server 22

Terms and privacy render with script and weren't readable (0). Data handling not read (0). A tool that maps old tool names to new calls eased the 3.0 change, no dates (5 of 20). Subprocessors not found (0). 0 + 0 + 5 + 0 = 5.

Kite 33

Hosted reading, for the platform and its remote MCP server. No public status page was found. None is linked from the docs or the footer, https://kite.new/status answers 404 and status.kite.new does not resolve (0). No readable incident history, so the floor (5). Limits are published with numbers on the account page, 200 agent actions a day on Free, reset at midnight UTC, unlimited on Pro; 60 new files an hour; 20 comments on one file every 10 minutes; 600 exported layers an hour; 20 keys; file caps of 400 MB and 250,000 layers. auth.md says registration and agent calls are rate-limited without a per-minute figure (12 of 15). 429 is documented in auth.md with 'back off' and no Retry-After, 401 with a refresh-once-then-rediscover rule, and the drawing guide says to edit layers in place rather than redraw; no idempotency key on any write and no safe-retry guidance for layer_draw, so a retried draw adds a second frame (6 of 15). No SLA. The terms (8 September 2026) say Kite is provided as is, uptime is not guaranteed and files may be lost (0). The hosted server carries no beta label and the registry entry is 1.0.0; the product launched on 6 October 2026 and the desktop apps are 0.1.16 (10). 0+5+12+6+0+10 = 33.

UX Pilot MCP server 15

No status page found (0). No history (5). No limits found (0). No retry guidance (0). No SLA (0). Not labelled beta (10). 0 + 5 + 0 + 0 + 0 + 10 = 15.

Kite 62

MCP reading, since the MCP server is the only surface an outside agent reaches. No tool input schemas were read. The server card at /.well-known/mcp/server-card.json declares tools without listing them, and llms-full.txt describes every tool in prose with argument names in the skill, so typed inputs are the vendor's to show and were not seen (10 of 25). llms.txt, llms-full.txt, skill.md, auth.md and pricing.md are served as text and Markdown (10). Descriptions say what each tool does and when to use it, such as file_search over file_list when the user describes a file, layer_edit rather than redrawing, never base64 in HTML, never a picture of a design, guide_read's six topics, and the view-only rule (16 of 20). Inputs named in the docs are typed in prose, with enumerations for audience (link, restricted), export formats (svg, react, tailwind, html), sticky colours, shader bases and guide topics, and bounds for videos (100 MB) and fonts (4 MB), but the main write tool takes one HTML string and layer_edit a free CSS object (8 of 15). Worked HTML examples in skill.md, a prompt per client page, and auth.md's 401, 400 and 429 responses; no example tool call or response and no MCP error shape (8 of 15). A dated changelog with 15 entries from 6 October to 1 November 2026 that names agent-facing changes (page, version, comment and export tools on 25 October), server version 1.0.0; no versioned tool surface or deprecation policy (10 of 15). 10+10+16+8+8+10 = 62.

UX Pilot MCP server 45

Schemas not read without sign-in (15 of 25). No llms.txt read (0). Tools grouped by job (find, organise, delete, import, review, React), with a help tool that maps old names to new calls (14 of 20). Inputs not verifiable (5 of 15). A tool that returns any action's fields with an example (8 of 15). Registry 3.0.0 on 4 November; no changelog (3 of 15). 15 + 0 + 14 + 5 + 8 + 3 = 45.

Kite 50

OAuth 2.1 with the authorization code flow, PKCE S256, dynamic registration of public clients, 7-day access tokens, 90-day refresh tokens that rotate on every use and revoke the connection if replayed, a revocation endpoint, bearer in the header only, and per-connection disconnect in Settings; one scope, pages, with the agent working under the user's full rights, and API keys that are per tool and revocable but unscoped (24 of 30). Least privilege comes from the file, not the token. A file shared view-only lets an agent read and comment but not draw, comment and download settings apply to agents, an agent cannot delete a file for good or touch the account, workspace or people, and each Mac-run request reaches only its file; no read-only mode on the hosted server and no confirmation for layer_remove, page_remove or version_restore (12 of 20). Comments, skills written by any editor, captured web pages and Figma pastes reach the model. The skill says a file's skills apply to that file only and never to sharing or people, and the Mac docs keep Agents Run Any Tool off by default because an agent reads comments and web pages and one could try to trick it; no guidance for the hosted server's own tools (8 of 15). Settings, Agents lists each connected app and key with when it connected and was last used, the board shows the agent's name while it works, and version history records agent saves; no per-call log for the operator (6 of 15). No security.txt (404), disclosure policy, bug bounty, SOC 2 or ISO 27001; SSO and SAML on Team (0 of 20). 24+12+8+6+0 = 50.

UX Pilot MCP server 39

OAuth or a bearer key; scopes not published (20 of 30). Organise tools never delete, and deletes need confirmation (14 of 20). Imported AI output and comments are third-party text; no injection guidance (3 of 15). No audit log (0). No security programme found (2 of 20). 20 + 14 + 3 + 0 + 2 = 39.

Kite 30

No x402, MPP or L402 in the docs, llms.txt, auth.md, the pricing pages or the terms (0). Plan prices are public and machine-readable at pricing.md, Free, Pro $20 per editor a month or $16 yearly, Team $35 or $28, with no per-call or per-action price since agent actions are counted on Free and unlimited on Pro (10 of 20). Free plan with 3 files and 200 agent actions a day, sign-up by emailed link or Google, no card mentioned anywhere (20). An agent can register itself as an OAuth client, but a person must sign up in a browser and click Allow, or make an API key in Settings (0). 0+10+20+0 = 30.

UX Pilot MCP server 20

No machine payment protocol (0). Pricing behind script, not read (0). Free tier (20). A person signs up (0). 0 + 0 + 20 + 0 = 20.