Skip to main content
Glama
Mateodioev

mcp-uxhints

by Mateodioev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-uxhints

No user-submitted related servers found.

    Related Servers

    • you-design-mcp

      nuttawutkpi
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-aware clients to query and use the you-design catalog of design systems, skills, and plugins at runtime via stdio.
      -

    • MCP Capability Matchmaker

      ywh0606
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP gateway and offline catalog CLI that aggregates multiple upstream MCP servers into a single stdio endpoint, and provides tool recommendation and catalog inspection without connecting to upstreams.
      MIT

    • McpHub

      John0King
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI tools to uniformly discover, inspect, and call tools, prompts, and resources from multiple upstream MCP servers through a small set of fixed MCP tools, over stdio or HTTP.
      2
      MIT

    • uxspot

      dockster
      A
      license
      Not graded
      quality
      D
      maintenance
      A remote MCP server exposing uxspot.io's curated UX glossary, AI tools directory, checklists, and Learn UX curriculum as callable tools. Enables AI assistants to search for UX terms, tools, and checklists via natural language.
      2
      MIT
    • yotta-dev-mcp by YottaMeta

      yotta-dev-mcpofficial

      YottaMeta
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides deterministic local development tools over stdio MCP, including repository mapping, code review, secret and dependency scanning, release checks, whitelisted checks, scaffolding, and workflow state tracking.
      718 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a distinct purpose: listing categories, listing hints with filters, searching, fetching a specific hint, retrieving a random hint, and refreshing the cache. There is no overlap in functionality; an agent can easily choose the correct tool based on intent.

    Naming Consistency4/5

    Tool names mostly follow a clear verb_noun pattern (list_, search_, get_, refresh_). 'random_hint' is a slight deviation since 'random' is not a verb, but it still reads as an imperative action and fits the overall snake_case convention. The inconsistency is minor.

    Tool Count5/5

    With 6 tools, the server is well-scoped for a catalog browsing and retrieval service. Each tool serves a unique, essential function without redundancy or bloat. The count is ideal for the domain.

    Completeness5/5

    The tool set covers all common read operations: list all (with category filters), search, get by id/slug, and get random. The refresh tool handles cache maintenance. Since this is a read-only hint catalog, there are no missing CRUD operations; the surface is complete for its purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources