uxspot-mcp server
io.github.dockster/uxspot-mcpdocksterstreamable-httpv1.1.0Scanned
uxspot.io UX reference: glossary, AI x UX tools directory, checklists and Learn UX curriculum
8 tools: 2 change things and 6 only read.
- Reads private data · 1
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 uxspot-mcp server can do
The uxspot-mcp server is published by the GitHub account dockster. It has 8 tools. It can create or change data (2 tools: define_term and spot_check), but cannot delete data. 6 tools only read.
1 tool reads private data (list_ux_tools).
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.
Last scanned Nov 19, 2026, version 1.1.0.
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.
8 tools
Changes things 2Claude Code: ask
define_termLook up one UX term: definition, why it matters in practice, honest reference numbers where they exist, an ASCII diagram for spatial concepts, and the source URL.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.
Description, as the server wrote it Look up one UX term: definition, why it matters in practice, honest reference numbers where they exist, an ASCII diagram for spatial concepts, and the source URL.
spot_checkPlay Spot Check — the uxspot daily UX vocabulary game — with the user.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.
Description, as the server wrote it Play Spot Check — the uxspot daily UX vocabulary game — with the user. Returns one quiz round: a UX term paired with a definition that is EITHER its real definition OR a plausible fake (a closely-related term's real definition), plus the answer and explanation. Show the user the term and the definition, ask "does this definition fit?", let them guess, then reveal. Call again for another round. Full daily game at https://uxspot.io/practice.
Only reads 6Show 6 read-only tools
get_checklistGet one checklist in full: every topic and every checkable item.No findings
Why it is in this group
- The name "get_checklist" says "get": a word for reading.
Description, as the server wrote it Get one checklist in full: every topic and every checkable item.
get_curriculumReturn the full Learn UX curriculum outline (13 sections, 78 topics) with URLs.No findings
Why it is in this group
- The name "get_curriculum" says "get": a word for reading.
Description, as the server wrote it Return the full Learn UX curriculum outline (13 sections, 78 topics) with URLs.
list_checklistsList the 5 interactive uxspot checklists with their topic and item counts.No findings
Why it is in this group
- The name "list_checklists" says "list": a word for reading.
Description, as the server wrote it List the 5 interactive uxspot checklists with their topic and item counts.
list_ux_toolsList the curated uxspot AI x UX design tools directory (54 tools across 6 categories), optionally filtered by category.Reads private dataNo findings
Why it is in this group
- The name "list_ux_tools" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "directory": it reads files.
Description, as the server wrote it List the curated uxspot AI x UX design tools directory (54 tools across 6 categories), optionally filtered by category.
search_curriculumSearch the Learn UX curriculum (78 topics) by keyword.No findings
Why it is in this group
- The name "search_curriculum" says "search": a word for reading.
Description, as the server wrote it Search the Learn UX curriculum (78 topics) by keyword. Returns matching topics with their HTML and raw-Markdown URLs.
search_glossarySearch the uxspot UX glossary (203 terms).No findings
Why it is in this group
- The name "search_glossary" says "search": a word for reading.
Description, as the server wrote it Search the uxspot UX glossary (203 terms). Returns matching terms with their plain-English definitions and source URLs.
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 untrusted-input or outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- 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.
Looked at Nov 20, 2026, 19:04 UTC, unchanged since Oct 22, 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
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://uxspot.io/mcp: tools/list returned 8 tools to an anonymous client, including define_term (write), spot_check (write)
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.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http uxspot https://uxspot.io/mcpclaude mcp add --transport http uxspot https://uxspot.io/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__uxspot__search_glossary",
"mcp__uxspot__list_ux_tools",
"mcp__uxspot__list_checklists",
"mcp__uxspot__get_checklist",
"mcp__uxspot__search_curriculum",
"mcp__uxspot__get_curriculum"
],
"ask": [
"mcp__uxspot__define_term",
"mcp__uxspot__spot_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 uxspot. Review it before you use it.
Capability tags behind 1 rule
- mcp__uxspot__list_ux_tools private-data
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/io.github.dockster/uxspot-mcp/verify?hash=f6ad0f72f4a150aea7ef7be79832ef4a6a1e7802ebbe498f3853ba74285653fd" | jq -e '.changed == false'Pinned hash f6ad0f72f4a1, from Nov 19, 2026, 14:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.dockster/uxspot-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.dockster/uxspot-mcp)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:32 UTC.
uxspot-mcp server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the uxspot-mcp server safe?
- No scan can promise that. What its definitions show: 8 tools, 2 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 uxspot-mcp server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the uxspot-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 uxspot-mcp server have?
- 8 tools: 2 write, 6 read. define_term, spot_check, search_glossary, list_ux_tools, list_checklists, get_checklist, search_curriculum and get_curriculum.
Does the uxspot-mcp server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the uxspot-mcp server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the uxspot-mcp server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.