Skip to main content
Glama
midodimori

stack-overflow-mcp-light

by midodimori
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to stack-overflow-mcp-light

No user-submitted related servers found.

    Related Servers

    • evo-scry

      krich11
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for internet search via direct Google and DuckDuckGo HTML scraping with AI-powered result normalization and optional summarization, requiring no API keys for search.
      MIT

    • serp-it

      luka-dev
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that aggregates web search results from multiple engines and optionally renders pages to Markdown, providing a unified search interface.
      7 npm
      3
      ISC

    • grok-mcp

      dq52099
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server providing web search, news search, and X/Twitter search capabilities via HTTP or stdio.
      -

    • bocha-mcp

      Johnhong9527
      F
      license
      A
      quality
      C
      maintenance
      MCP server for Bocha Search API, enabling web search and AI-powered search with customizable parameters like result count, freshness, and summaries.
      2
      1
      -
    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

    B3.4/5.0

    Scored across 3 tools

    Disambiguation3/5

    search_questions and search_questions_by_tag overlap because search_questions accepts advanced filters that likely include tag filtering, making the distinction unclear. fetch_question_answers is clearly distinct, retrieving a specific question with answers, but the two search tools create ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: search_questions, search_questions_by_tag, and fetch_question_answers. The 'by_tag' modifier is a clear exception for the second search tool but still follows the same convention, making the naming predictable and uniform.

    Tool Count4/5

    With 3 tools, the set is on the lean side but appropriate for a 'light' Stack Overflow read-only server. Each tool serves a core purpose without redundancy, and the count is reasonable for the intended narrow scope.

    Completeness4/5

    The server covers essential read operations: searching questions generically and by tag, and fetching a question with answers. Missing operations like user lookups or comment retrieval are not critical for a lightweight server, but the surface is slightly thin for full Stack Overflow coverage.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources