Skip to main content
Glama
sevenboom77

ResearchTwin MCP Server

by sevenboom77
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ResearchTwin MCP Server

No user-submitted related servers found.

    Related Servers

    • Argon Memory

      Tangtaizong-BUAA
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP agents to maintain durable, evidence-aware project knowledge, retrieve precise excerpts on demand, and track decisions, conflicts, and revisions across sessions.
      1
      Apache 2.0

    • SWEGCA-VRS-MCP

      raspie10032
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to persistently record experiences, recall related episodes, run VRS convergence, and manage bounded world-state through MCP tools.
      MIT

    • Munnin

      alvseek
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to maintain a persistent identity and structured memory—including reasoning patterns, episodic history, and knowledge—while exposing procedures for managing that memory over MCP.
      Apache 2.0

    • big-brAIn

      jasonpaige
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding tools and developers to store, search, and supersede durable engineering discoveries with temporal validity, and to coordinate active work across sessions via MCP.
      MIT

    • AgentBase

      vhspace
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to persistently store and semantically search shared knowledge via MCP tools.
      2
      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.5/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools target distinct entities and actions, and the record_*/list_*/update_* prefixes help separate workflows. There is some potential confusion between record_research_activity and update_project_status, or between candidate intelligence and intelligence briefs, but the descriptions clarify the differences.

    Naming Consistency5/5

    All tool names use a consistent snake_case verb_noun pattern, such as record_*, list_*, update_*, get_*, and sync_*. The naming is predictable and makes the purpose of each tool immediately understandable.

    Tool Count4/5

    At 16 tools, the server is slightly above the typical 3-15 well-scoped range, but the tools map to a broad but coherent set of research workflows: tracking, reporting, candidate intelligence, and knowledge sync. Each tool has a defined role, so the count is reasonable.

    Completeness4/5

    The tool surface covers the main lifecycle stages: recording activities and status, managing advisor instructions, triaging candidates, generating reports, and syncing project knowledge. Minor gaps exist, such as no update/delete for activities or briefs, but these feel like intentional append-only patterns rather than blocking omissions.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources