Skip to main content
Glama
flo7up

AIUseCaseHub MCP

by flo7up
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to AIUseCaseHub MCP

No user-submitted related servers found.

    Related Servers

    • Ghost + Contentful MCP

      robsoncoelho
      F
      license
      A
      quality
      D
      maintenance
      Enables 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
      -

    • oss-mcp

      sblattj
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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

    • skillhub-mcp-server

      q15004040209-creator
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to discover, retrieve, and invoke 80+ SkillHub practical skills as standardized MCP tools over stdio, covering coding, office, content creation, data analysis, and security operations.
      MIT No Attribution
    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

    A3.9/5.0

    Scored across 4 tools

    Disambiguation2/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources