AIUseCaseHub MCP
Related Servers
Alternatives to AIUseCaseHub MCP
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceEnables AI assistants to search blog posts and pages from Ghost, and learn pages, case studies, and events from Contentful. Provides five search tools with contextual snippets via MCP stdio transport.5-
- AlicenseBqualityBmaintenanceConnects Claude, ChatGPT, Microsoft Copilot, and other MCP clients to an AssetLab asset management account, letting users query and manage work orders, PM schedules, capital projects, infrastructure networks, and other records in plain language. It exposes 480+ scoped, tenant-bound, audited tools with both read and write access, hosted or run locally over stdio.481266 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients such as Claude, Claude Code and Cursor to keyword-search a directory of over 1,000 hand-picked productivity tools, apps, AI tools, courses and books, filtering by category, type, pricing and result limit, and to fetch a single listing by slug, page URL or exact name and list all categories with counts. It runs read-only over stdio with no API key, dependencies or tracking, making only a plain GET of the public catalogue.MIT
- AlicenseAqualityBmaintenanceStdio proxy for HirePulse: 27 live tools for company research, hiring, job changes, public contacts and commerce evidence. Focused remote profiles: 9 B2B or 11 commerce tools. Free sandbox, 10 successful calls per agent per UTC day (shared network ceiling), and eligible 25-call trials. Paid results use x402 USDC on Base. Install: npx -y hirepulse-mcp (Node.js 20+).2689 npmMIT
- AlicenseAqualityCmaintenanceEnables AI tools to search a directory of practical AI agent use cases by keyword, category, and minimum trust score, and to retrieve full entry details such as trust score breakdowns, setup prompts, tools, models, and runtime locations. It is read-only and returns links back to the source directory.216 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to discover open-source libraries worth reusing through multi-signal repository ranking and to search real code with sub-50ms local regex/semantic queries federated to live GitHub, grep.app, and package-registry backends. It exposes seven tools over stdio—repo search, code search, repo profile/tree, file and docs fetching, and a usage guide—with structured filters, typed pre-execution errors, and a byte-identical CLI twin.MIT
TDQS
Scored across 4 tools
search_usecases and hybrid_search_usecases are nearly the same operation—both perform hybrid full-text/vector ranking—and the only clear distinction is that the latter adds filters. An agent will struggle to know which to choose. vector_search_usecases and get_usecase_details are distinct, but the overlapping search tools create real ambiguity.
All tool names follow a consistent verb_noun snake_case pattern: search_usecases, hybrid_search_usecases, vector_search_usecases, get_usecase_details. The prefixes and suffixes are predictable and readable.
Four tools is a reasonable size for a focused use-case search and detail server. However, one of the four tools is largely redundant with another, so the count is slightly padded rather than perfectly minimal.
The server covers the core workflow of discovering AI use cases via search and then fetching full details. It lacks an explicit browse/list-all or filter-only endpoint, but the search tools likely handle most discovery needs, so the gaps are minor.