Skip to content

Candor UI docs MCP server

com.themethodic/candorthemethodic.comstreamable-httpv6.15.1Scanned

Candor UI docs and component suggestions. Read-only, no key, never serves paid source.

12 tools: 1 change things and 11 only read.

Tools: 0 delete, 0 irreversible, 1 write, 11 read.
  • Reads private data · 5
  • Reads text others write · 3
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Candor UI docs MCP server can do

The Candor UI docs MCP server is published by themethodic.com, a domain the MCP Registry verified. It has 12 tools. It can create or change data (1 tool: theme_check), but cannot delete data. 11 tools only read.

5 tools read private data (search_docs, get_component_docs, list_components and 2 more); 3 tools bring in text other people can write (list_components, get_started and get_review_checklist).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 9 times since Anlyon Radar first saw them.

Last scanned Nov 21, 2026, version 6.15.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

12 tools

Changes things 1Claude Code: ask
  • theme_checkCheck a brand file (candor-brand.css, or any CSS that sets Candor's tokens) the way `npx candor-ui theme check` does: colour contrast of every text and edge pairing in light, dark …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Check a brand file (candor-brand.css, or any CSS that sets Candor's tokens) the way `npx candor-ui theme check` does: colour contrast of every text and edge pairing in light, dark and high contrast, each with its ratio and the ratio it needs, for the base and then for each brand scope ([data-brand="<name>"], as the theme builder writes several brands in one file) as a theme of its own, labelled (Light in [data-brand="acme"]) and counted in the totals; then the --cd-motion-* and --cd-sound-* values against the motion manifest; then token names and data-slot selectors against the token manifest, as warnings that don't fail the check (a --cd-* name the kit doesn't read, with the nearest one it does; a value outside a token's range; a --cd-show-* or --cd-draw-* value the Pro motion-drawings item has no drawing for, as motion-value, with the values it takes; an internal --cd-* name a brand file shouldn't set; a [data-slot] selector no component renders). Call it with the file's contents after you edit candor-brand.css, and fix what it reports before you say the theme is done. Returns a short summary (failures first, with a suggested lightness that would pass; findings with file, line and the fix), then the findings as JSON (ok, motionChecked, counts, themes with every pairing and, for a brand scope's, its brand, suggestions, motionAndSound.findings, tokens.findings). Anything it can't read (a color-mix(), a var(), a sound file) is reported as not measured, never as a pass. Sound files are not measured here: the server can't see your public/ folder, so `npx candor-ui theme check` in the project does that. It checks against the current kit; an older @candor-kit in the file is checked against the current names, with a note. It reads only the CSS you send, follows no @import and fetches nothing. At most 256 KB. Example arguments: { "css": ":root { --primary: oklch(0.55 0.2 260); --cd-motion-pop-dur: 140ms; }", "filename": "candor-brand.css" }

    Annotations the server declares

    • title: Check a Candor brand file
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 11Show 11 read-only tools
  • get_briefOne item's brief to hand to the coding agent that builds the screen: the same Markdown the docs page's "Copy for a coding agent" button copies (what the item is, its tier and insta…Reads private dataNo findings

    Why it is in this group

    • The name "get_brief" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "doc": it reads documents.
    Description, as the server wrote it
    One item's brief to hand to the coding agent that builds the screen: the same Markdown the docs page's "Copy for a coding agent" button copies (what the item is, its tier and install command, an example with the import paths an app uses, every prop, the string keys, and the rules to keep).

    Annotations the server declares

    • title: A brief for a coding agent
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_component_docsRead one item's docs as Markdown: what it is, its tier and install command, an example with the import paths an app uses, every prop, function, type, and the LocaleProvider string …Reads private dataNo findings

    Why it is in this group

    • The name "get_component_docs" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_component_docs" says "get" and "doc": it reads documents.
    • private-dataThe description's first sentence says "read" and "doc": it reads documents.
    Description, as the server wrote it
    Read one item's docs as Markdown: what it is, its tier and install command, an example with the import paths an app uses, every prop, function, type, and the LocaleProvider string keys.

    Annotations the server declares

    • title: Read a Candor UI docs page
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_designThe design system as Markdown: every colour role and what it's for, the type scale, radius, shadows, motion, density and themes, read from the shipped CSS; how an app re-tokens for…No findings

    Why it is in this group

    • The name "get_design" says "get": a word for reading.
    Description, as the server wrote it
    The design system as Markdown: every colour role and what it's for, the type scale, radius, shadows, motion, density and themes, read from the shipped CSS; how an app re-tokens for its brand; and how to build the screens around Candor components (surfaces, rhythm, writing, do and don't).

    Annotations the server declares

    • title: Candor UI's design system
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_patternRead a pattern as Markdown: a common problem in agent UIs (approvals, traces, cost guards, …) and the components that solve it.No findings

    Why it is in this group

    • The name "get_pattern" says "get": a word for reading.
    Description, as the server wrote it
    Read a pattern as Markdown: a common problem in agent UIs (approvals, traces, cost guards, …) and the components that solve it.

    Annotations the server declares

    • title: Read a Candor UI pattern
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_review_checklistThe checklist to run after each screen where an AI agent acts, before moving on: one line per check, each tied to a rule (model output is text, unknown stays unknown, a locked cont…Reads text others writeNo findings

    Why it is in this group

    • The name "get_review_checklist" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe name "get_review_checklist" says "get" and "review": it reads comments, which other people can write.
    Description, as the server wrote it
    The checklist to run after each screen where an AI agent acts, before moving on: one line per check, each tied to a rule (model output is text, unknown stays unknown, a locked control says why, nothing pre-selected, approve the exact change, reasoning is believed, the app names the agent, say what can be undone, plus status, progress and accessibility). From the candor-agent-ui skill; works with or without Candor.

    Annotations the server declares

    • title: Review checklist for agent UI screens
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_screenRead one screen as Markdown: what it's for, two or three layouts with when to pick each, the Candor UI items that build each (with tiers), an install command, the honesty rules tha…No findings

    Why it is in this group

    • The name "get_screen" says "get": a word for reading.
    Description, as the server wrote it
    Read one screen as Markdown: what it's for, two or three layouts with when to pick each, the Candor UI items that build each (with tiers), an install command, the honesty rules that matter most on it, and a brief to hand to the coding agent that builds it.

    Annotations the server declares

    • title: Read a screen from the catalogue
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_startedHow to install Candor UI in a React or Next.js app, render a chat, connect an agent SDK, add licensed items and keep them updated.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_started" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "chat": it reads messages.
    • untrusted-inputThe description's first sentence says "chat": it reads messages, which other people can write.
    Description, as the server wrote it
    How to install Candor UI in a React or Next.js app, render a chat, connect an agent SDK, add licensed items and keep them updated. With `prompt: true`, only "Give this to your agent": one block of text for adopting Candor into an app that already exists (it asks about the stack and the agent's API first, installs with the CLI, leaves the licence key to the person and names the providers to wrap the app in).

    Annotations the server declares

    • title: How to set up Candor UI
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_componentsList every item by group (Chat, Agent work, App shell, …; the app scaffolding groups, Layout, Charts, Team, Billing and Admin, after the agent groups), or one group's items with de…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "list_components" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "chat": it reads messages.
    • untrusted-inputThe description's first sentence says "list" and "chat": it reads messages, which other people can write.
    Description, as the server wrote it
    List every item by group (Chat, Agent work, App shell, …; the app scaffolding groups, Layout, Charts, Team, Billing and Admin, after the agent groups), or one group's items with descriptions.

    Annotations the server declares

    • title: List Candor UI components
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_screensList the screen catalogue by area (talking to the agent, approving and controlling, watching the work, …), one line per screen: what it's for and its slug.No findings

    Why it is in this group

    • The name "list_screens" says "list": a word for reading.
    Description, as the server wrote it
    List the screen catalogue by area (talking to the agent, approving and controlling, watching the work, …), one line per screen: what it's for and its slug. Read one with get_screen.

    Annotations the server declares

    • title: List the screens an agent product needs
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_docsSearch Candor UI's components, hooks, blocks and patterns by what they do ("approve a tool call", "cost estimate", "session list").Reads private dataNo findings

    Why it is in this group

    • The name "search_docs" says "search": a word for reading.

    What it can reach

    • private-dataThe name "search_docs" says "search" and "doc": it reads documents.
    Description, as the server wrote it
    Search Candor UI's components, hooks, blocks and patterns by what they do ("approve a tool call", "cost estimate", "session list"). Returns names, tiers and one-line descriptions; read one with get_component_docs.

    Annotations the server declares

    • title: Search Candor UI docs
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • suggest_componentsDescribe the screen or feature you're building; get the Candor UI items that fit, why, the matching patterns and screens, and an install command per tier.No findings

    Why it is in this group

    • The description's first verb is "describe": a word for reading.
    Description, as the server wrote it
    Describe the screen or feature you're building; get the Candor UI items that fit, why, the matching patterns and screens, and an install command per tier. When nothing in Candor fits, it says so rather than suggesting something close. Pass `sdk` so only your agent SDK's adapter is suggested. Read each suggestion's docs before using it.

    Annotations the server declares

    • title: Suggest Candor UI components
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data5
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:20 UTC, unchanged since Nov 15, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://candor.themethodic.com/mcp: tools/list returned 13 tools to an anonymous client, including item_changes (irreversible), theme_check (write)

    What this check looks for

Posture changes

  1. Nov 15, 2026
    • Tools that change things, listed without credentials: 0 to 2

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 removed, 7 changed.−1 removed~7 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 0 -> 2.View diff
    • Tools that change things, listed without credentials: 0 to 2
  3. Tools1 changed.~1 changedView diff
  4. Tools1 changed.~1 changedView diff
  5. Tools1 changed.~1 changedView diff
  6. Tools8 changed.~8 changedView diff
  7. Tools1 added.+1 addedView diff
    • Added:item_changesCan't be undone
  8. Tools1 changed.~1 changedView diff
  9. Tools1 added.+1 addedView diff
  10. Tools2 added.+2 addedView diff

Install

Pinned to version 6.15.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http candor https://candor.themethodic.com/mcp
claude mcp add --transport http candor https://candor.themethodic.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__candor__search_docs",
      "mcp__candor__get_component_docs",
      "mcp__candor__suggest_components",
      "mcp__candor__list_components",
      "mcp__candor__get_pattern",
      "mcp__candor__list_screens",
      "mcp__candor__get_screen",
      "mcp__candor__get_started",
      "mcp__candor__get_brief",
      "mcp__candor__get_design",
      "mcp__candor__get_review_checklist"
    ],
    "ask": [
      "mcp__candor__theme_check"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as candor. Review it before you use it.

Capability tags behind 6 rules
  • mcp__candor__search_docs private-data
  • mcp__candor__get_component_docs private-data
  • mcp__candor__list_components private-data, untrusted-input
  • mcp__candor__get_started private-data, untrusted-input
  • mcp__candor__get_brief private-data
  • mcp__candor__get_review_checklist untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.themethodic/candor/verify?hash=08ca97a7edaaa1c5768746f0f457d30a0faa54eef01d908a932ce27d86b8ad85" | jq -e '.changed == false'

Pinned hash 08ca97a7edaa, from Nov 21, 2026, 01:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.themethodic/candor/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.themethodic/candor
[![Anlyon Radar](https://radar.anlyon.com/badge/com.themethodic/candor.svg)](https://radar.anlyon.com/servers/com.themethodic/candor)

Source: MCP Registry · repository. Synced Nov 21, 2026, 01:17 UTC.

Candor UI docs MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Candor UI docs MCP server safe?

No scan can promise that. What its definitions show: 12 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Candor UI docs MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Candor UI docs MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Candor UI docs MCP server have?

12 tools: 1 write, 11 read. theme_check, search_docs, get_component_docs, suggest_components, list_components, get_pattern, list_screens, get_screen and 4 more.

Does the Candor UI docs MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Candor UI docs MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Candor UI docs MCP server changed its tools?

Yes, 9 times since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.