Skip to main content
Glama
Zine-Elabidine

research-mcp

by Zine-Elabidine
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to research-mcp

No user-submitted related servers found.

    Related Servers

    • deep-websearch

      2046698389-code
      A
      license
      A
      quality
      C
      maintenance
      Enables configuration-driven, budgeted multi-source web research across platform and web search adapters, merging duplicate links, preserving provenance, and returning honest source coverage reports.
      4
      MIT

    • scilib

      Hiran001
      A
      license
      A
      quality
      A
      maintenance
      Enables federated search across open-access scientific literature, legal full-text retrieval with provenance, and full-text search over papers already stored locally.
      14
      MIT

    • Infobroker

      flukeatzerocool
      A
      license
      A
      quality
      A
      maintenance
      An MCP-native research assistant — search backend, intent-routing, and writing pipeline that carries a question through search, verification, and writing, delivering whatever research you need: quick answers, verified sources, or a finished document.
      4
      7
      388 npm
      MIT
    • genpark-deep-research-consensus-engine-skill by alphaparkinc

      genpark-deep-researchofficial

      alphaparkinc
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and MCP clients to run deterministic deep research consensus arbitration by parsing queries, evaluating source authority and contradictions, and returning structured JSON dossiers and telemetry.
      8
      -

    • research-dispatcher-mcp

      0x67108864
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to run research queries across multiple public sources (Hacker News, Reddit, GitHub, Brave Search) in parallel, returning normalized results.
      5
      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.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct evidence layer: search_community covers lived experience, search_web covers published claims, search_demand covers transactions and workarounds, and read_discussion is an explicit follow-up for thread-level depth. The meta tools (corpus_stats, providers_status) are clearly separated from search operations, so there is no real ambiguity.

    Naming Consistency4/5

    The search_* tools are consistently named with a clear verb_noun pattern, and read_discussion follows suit. corpus_stats and providers_status are descriptive and readable but don't follow the verb-first pattern, creating a minor stylistic inconsistency rather than confusion.

    Tool Count5/5

    Six tools is a well-scoped size for a research assistant. Each tool earns its place: three distinct search layers, one deep-dive reader, and two diagnostic/infrastructure tools that support the search workflow without bloating the surface.

    Completeness4/5

    The set covers the core research loop well: finding lived-experience evidence, published claims, demand signals, reading full Reddit threads, checking corpus depth, and diagnosing provider issues. The main gaps are lack of direct arbitrary URL/content fetching and no obvious way to query the accumulated corpus itself beyond stats.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources