Skip to main content
Glama
Sign In
research-scope-mcp

research-scope-mcp

by AxelVerneBooks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to research-scope-mcp

No user-submitted related servers found.

    Related Servers

    • GnosisLab

      cloudcell
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents and MCP clients to run research as an explicit scientific process: forming hypotheses, designing and executing sealed experiments, capturing observations and artifacts, linking claims to supporting evidence, and reviewing provenance. Exposes coordinated MCP services so users can inspect, reproduce, and audit every step from question to conclusion rather than trusting an opaque final answer.
      46
      162 PyPI
      21
      Apache 2.0
    • genpark-multihop-research-query-decomposer-skill

      genpark-multihop-researchofficial

      alphaparkinc
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables decomposition of complex research queries into multi-hop sub-queries and synthesis DAGs, with scientific consensus analysis, citation credibility verification, and deterministic JSON outputs for MCP-compliant clients.
      8
      -

    • periscope-mcp

      NLY22
      A
      license
      C
      quality
      B
      maintenance
      Gives any MCP client 27 tools for turning scattered feeds, forums, and media into a persistent, searchable evidence corpus, so an agent can search and import evidence, verify claims with independent-source counting and citation checks, and run multi-round research that produces cited, revisable reports. It also supports adaptive retrieval widening, tiered evidence where only author-written sections count as sources, and honest degradation when no LLM key is available.
      27
      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

    A3.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool occupies a distinct stage of a linear research pipeline: plan_research (planning), fetch_and_score (acquisition), build_report (assembly), and check_report (verification). There is no overlap in purpose, so an agent can select unambiguously.

    Naming Consistency4/5

    All names use snake_case with a verb-led pattern (plan_research, build_report, check_report), which is predictable and readable. fetch_and_score is the one deviation, using a compound verb_and_verb form rather than verb_noun, but it remains clear.

    Tool Count4/5

    Four tools is well-scoped for a focused research workflow, with each tool earning its place as a pipeline stage. It is slightly lean, as there is no dedicated source-discovery step, but nothing is redundant.

    Completeness4/5

    The surface covers the full lifecycle: plan, fetch+score, build, and verify, including a citation registry and orphan-claim checking. The main gap is source discovery/search, leaving the agent to supply URLs itself, but core workflows have no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources