_ registry / mcp streamable-http · checked 1h ago

uxspot

https://uxspot.io

Registry code: 4d56f79c9c2aabd4

api record

uxspot.io UX reference. Use these tools to define UX glossary terms, browse the curated AI x UX tools directory, read the interactive checklists, and search the Learn UX curriculum. Cite the returned uxspot.io URLs.

endpoint
https://uxspot.io/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is uxspot live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is uxspot free to use?
Yes — the hub reached it with no key and no payment.
What tools does uxspot have?
8 tools: define_term, get_curriculum, list_checklists, search_glossary, list_ux_tools, search_curriculum, get_checklist, spot_check.
Is uxspot safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.5%

90 days 99.4%· all time 99.4%

latency
247ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 533 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
education & learning learning & tutoring
used for
  • define a ux term
  • browse ux checklists
  • search a ux curriculum
  • list ai ux design tools
takes → gives
text → text, data
tools
8 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
7 open 1 never probed 7 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_curriculum reads open 8h ago

    Return the full Learn UX curriculum outline (13 sections, 78 topics) with URLs.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • list_checklists reads open 8h ago

    List the 5 interactive uxspot checklists with their topic and item counts.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • search_glossary reads open 18h ago

    Search the uxspot UX glossary (203 terms). Returns matching terms with their plain-English definitions and source URLs.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "Text to match against term names and definitions."
    }
  }
}
    arguments 12 lines
  • list_ux_tools reads open 8h ago

    List the curated uxspot AI x UX design tools directory (54 tools across 6 categories), optionally filtered by category.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "category": {
      "enum": [
        "Brainstorm & Research",
        "AI Design & Prototyping",
        "Usability Testing & Analytics",
        "UX Writing & Content",
        "Web & App Builders",
        "Project Management"
      ],
      "type": "string",
      "description": "Optional category filter."
    }
  }
}
    arguments 17 lines
  • search_curriculum reads open 23h ago

    Search the Learn UX curriculum (78 topics) by keyword. Returns matching topics with their HTML and raw-Markdown URLs.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "Keyword to match against topic titles and section names."
    }
  }
}
    arguments 12 lines
  • get_checklist reads open 23h ago

    Get one checklist in full: every topic and every checkable item.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Checklist slug: ux, ds, ai, a11y, or usability."
    }
  }
}
    arguments 12 lines
  • spot_check reads open 23h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • define_term reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "term"
  ],
  "properties": {
    "term": {
      "type": "string",
      "description": "The exact or approximate term to define, e.g. \"empathy map\"."
    }
  }
}
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 4d56f79c9c2aabd4.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4d56f79c9c2aabd4/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/4d56f79c9c2aabd4/badge.svg)](https://brick.blue/agent/4d56f79c9c2aabd4?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.