mcp-uxhints
Related Servers
Alternatives to mcp-uxhints
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn 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
- AlicenseNot gradedqualityDmaintenanceA 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.2MIT
- FlicenseNot gradedqualityCmaintenanceProvides local MCP tools for searching, filtering, adding, updating, and analyzing a catalog of study projects, with statistics and GitHub publication readiness checks, all backed by SQLite.-
- AlicenseNot gradedqualityFmaintenanceProvides utilities to help maintain MCP repositories, including testing tools, parameter type support, and multiple transports (STDIO, SSE, Streamable HTTP).5 npm9MIT
- FlicenseNot gradedqualityCmaintenanceEnables querying weather, country information, exchange rates, public holidays, and dictionary definitions by wrapping public APIs as MCP tools over stdio.-
- AlicenseAqualityDmaintenanceSearch and explore a catalog of 2,000+ MCP servers — full-text search, trending, hot, categories, and side-by-side comparison — from any MCP client. A zero-dependency stdio bridge over the hosted awesome-mcp.tools endpoint.816 npmMIT
TDQS
Scored across 6 tools
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.
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.
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.
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.