Skip to main content
Glama
ScienceLiveHub

Replication Radar

by ScienceLiveHub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Replication Radar

No user-submitted related servers found.

    Related Servers

    • research.md

      eidos-agi
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enforces evidence-graded, phase-gated, peer-reviewed research workflows for AI agents to conduct rigorous decision-making.
      MIT
    • airas by airas-org

      airasofficial

      airas-org
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for AIRAS, an open-source research automation platform. It provides tools for paper search, retrieval, hypothesis generation, experiment execution, and paper writing, enabling automated or interactive research directly from MCP clients.
      35
      MIT

    • mcp-openalex

      ELumya
      A
      license
      A
      quality
      D
      maintenance
      MCP server for the OpenAlex scholarly database, providing AI agents with tools to search and retrieve academic works, authors, and institutions via natural language queries.
      8
      MIT

    • Scholar MCP Server

      mlintangmz2765
      A
      license
      A
      quality
      C
      maintenance
      Unified MCP server for scientific literature search and extraction, integrating databases like Scopus, OpenAlex, Semantic Scholar, and Unpaywall to enable AI agents to discover papers, track citations, and analyze content.
      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

    A4.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of the replication workflow: radar discovers papers to replicate, find_independent_software locates reusable software, replication_status checks whether a specific DOI has been verified, verified_claims lists all verified claims, replication_template provides the production template, and find_dataset delegates to another MCP. No two tools overlap in purpose.

    Naming Consistency2/5

    Naming patterns are inconsistent: 'radar' is a noun command, while others use verb_noun (find_*), noun phrases (replication_status, replication_template), and adjective_noun (verified_claims). There's no consistent verb convention across the set.

    Tool Count5/5

    Six tools cover the discovery, status, software, dataset, template, and verified-claims aspects of replication without redundancy. Neither sparse nor bloated.

    Completeness5/5

    Covers the full discovery-to-production loop: targets (radar), verification status (replication_status), verified claims list, software and dataset finding, and the actual replication template. The dataset handoff is an intentional delegation to another MCP, not a gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources