ResearchTwin

io.github.martinfraschPublished by GitHub account martinfraschv0.1.1Updated Oct 24, 2026

Federated research discovery with S-Index metrics across a network of digital twins.

Overview

AI-generated overview

A local MCP server that connects an assistant to the ResearchTwin federated research network for discovering researchers, papers, datasets and repositories.

What you can do
Query researcher profiles and their publications, datasets and code repositories through the ResearchTwin discovery API, including citation and S-Index metrics where available. Search across researchers by keyword and result type such as papers. Reach a hosted ResearchTwin instance or a self-run local node, depending on the configured base URL.
When to use it
Useful when an assistant needs to look up scholarly output, researcher profiles or S-Index metrics from the ResearchTwin network, or to explore federated research discovery data during a literature or collaboration search.
Requirements
Runs locally as a Python package launched with uvx (Python runtime needed). Network access to a ResearchTwin API endpoint, set via the RESEARCHTWIN_URL environment variable (defaults to the hosted researchtwin.net service). No authentication is declared for the MCP server itself.
Before you install
Queries go to the configured ResearchTwin endpoint, which by default is a third-party hosted service, so research queries and identifiers leave the machine. Pointing RESEARCHTWIN_URL at a self-hosted node changes who receives that data. The README's self-hosting path mentions separate API keys for the platform itself, which are not part of this MCP server's configuration.

Installation

In SourceWeft

  1. Open ResearchTwin in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

ResearchTwin: Federated Agentic Web of Research Knowledge

[arXiv] [License] [Live Platform] [S-Index Spec] [Project Board]

ResearchTwin is an open-source, federated platform that transforms a researcher's publications, datasets, and code repositories into a conversational Digital Twin. Built on a Bimodal Glial-Neural Optimization (BGNO) architecture, it enables dual-discovery where both humans and AI agents collaborate to accelerate scientific discovery.

Live at researchtwin.net | Join the Network | Read the Paper (arXiv)


Project Vision

The exponential growth of scientific outputs has created a "discovery bottleneck." Traditional static PDFs and siloed repositories limit knowledge synthesis and reuse. ResearchTwin addresses this by:

  • Integrating multi-modal research artifacts from Semantic Scholar, Google Scholar, GitHub, and Figshare
  • Computing a real-time S-Index metric (Quality × Impact × Collaboration) across all output types
  • Providing a conversational chatbot interface for interactive research exploration
  • Exposing an Inter-Agentic Discovery API with Schema.org types for machine-to-machine research discovery
  • Enabling a federated, Discord-like architecture supporting local nodes, hubs, and hosted edges

Architecture Overview

BGNO (Bimodal Glial-Neural Optimization)

Data Sources          Glial Layer          Neural Layer         Interface┌──────────────┐    ┌─────────────┐    ┌──────────────┐    ┌────────────┐│Semantic Scholar│───▶│             │    │              │    │  Web Chat  ││Google Scholar │───▶│  SQLite     │───▶│  RAG with    │───▶│  Discord   ││GitHub API     │───▶│  Cache +    │    │  Claude API  │    │  Agent API ││Figshare API   │───▶│  Rate Limit │    │              │    │  Embed     │└──────────────┘    └─────────────┘    └──────────────┘    └────────────┘
  • Connector Layer: Pulls papers (S2+GS with deduplication), repos (GitHub), datasets (Figshare), and ORCID metadata
  • Glial Layer: SQLite caching with 24h TTL, rate limiting, S2+GS title-similarity merge (0.85 threshold)
  • Neural Layer: RAG with Claude — context assembly, prompt engineering, conversational synthesis
  • Interface Layer: D3.js knowledge graph, chat widget, Discord bot, REST API

Federated Network Tiers

TierNameDescriptionStatus
Tier 1Local NodesResearchers run python run_node.py locallyLive
Tier 2HubsLab aggregators federating multiple nodesPlanned
Tier 3Hosted EdgesCloud-hosted at researchtwin.netLive

Inter-Agentic Discovery API

Machine-readable endpoints with Schema.org @type annotations:

EndpointSchema.org TypePurpose
GET /api/researcher/{slug}/profilePersonResearcher profile with HATEOAS links
GET /api/researcher/{slug}/papersItemList of ScholarlyArticlePapers with citations
GET /api/researcher/{slug}/datasetsItemList of DatasetDatasets with QIC scores
GET /api/researcher/{slug}/reposItemList of SoftwareSourceCodeRepos with QIC scores
GET /api/discover?q=keyword&type=paperSearchResultSetCross-researcher search

Getting Started

Hosted (Tier 3) — Zero Setup

  1. Visit researchtwin.net/join.html
  2. Register with your name, email, and research identifiers
  3. Your Digital Twin is live immediately

Local Node (Tier 1) — Full Control

bash
git clone https://github.com/martinfrasch/researchtwin.gitcd researchtwinpip install -r backend/requirements.txtcp node_config.json.example node_config.json# Edit node_config.json with your detailspython run_node.py --config node_config.json

Docker Deployment

bash
cp .env.example .env  # Add your API keysdocker-compose up -d --build

Required API keys: ANTHROPIC_API_KEY (for Claude RAG) Optional: S2_API_KEY, GITHUB_TOKEN, DISCORD_BOT_TOKEN, SMTP credentials


Repository Structure

researchtwin/├── backend/│   ├── main.py              # FastAPI endpoints (REST + Discovery API)│   ├── researchers.py        # SQLite researcher CRUD + token management│   ├── database.py           # SQLite schema, WAL mode, migrations│   ├── models.py             # Pydantic models for all endpoints│   ├── rag.py                # RAG context assembly for Claude│   ├── qic_index.py          # S-Index / QIC computation engine│   ├── email_service.py      # SMTP service for profile update codes│   ├── connectors/           # Data source connectors│   │   ├── semantic_scholar.py│   │   ├── scholarly_lib.py  # Google Scholar via scholarly│   │   ├── github_connector.py│   │   └── figshare.py│   └── discord_bot/          # Discord bot with /research and /sindex├── frontend/│   ├── index.html            # Main dashboard with D3.js knowledge graph│   ├── join.html             # Self-registration page│   ├── update.html           # Email-verified profile updates│   ├── privacy.html          # Privacy policy│   └── widget-loader.js      # Embeddable chat widget├── run_node.py               # Tier 1 local node launcher├── node_config.json.example  # Local node configuration template├── docker-compose.yml        # Docker orchestration├── nginx/                    # Nginx reverse proxy + SSL└── whitepaper.tex            # LaTeX manuscript

Ecosystem

This repository is part of the ResearchTwin Ecosystem project:

RepositoryDescription
researchtwinFederated platform (this repo)
s-indexS-Index formal specification and reference implementation

Embeddable S-Index Widget

Show your S-Index on your lab website, Google Sites page, or personal homepage:

html
<iframe  src="https://researchtwin.net/embed.html?slug=YOUR-SLUG"  width="440" height="180"  style="border:none; border-radius:12px;"  loading="lazy"></iframe>

Replace YOUR-SLUG with your researcher slug (e.g. martin-frasch).

Google Sites: Edit page > Insert > Embed > "By URL" tab > paste https://researchtwin.net/embed.html?slug=YOUR-SLUG

WordPress: Add a Custom HTML block and paste the iframe code.

The widget displays the researcher's name, S-Index score, h-index, citation count, and paper count. Data updates automatically from live API sources.

See it in action | Full embed instructions


Documentation

DocumentDescription
API ReferenceFull REST API documentation with schemas and examples
Self-Hosting GuideTier 1 Local Node setup and configuration
Hub Federation GuideTier 2 Hub architecture and setup (planned)
Security PolicyVulnerability reporting and security best practices

Contributing

Contributions welcome! See the project board for tracked issues.

  • New connectors (ORCID enrichment, PubMed, OpenAlex)
  • Affiliation-based geographic mapping
  • MCP server for inter-agentic discovery
  • UI/UX improvements
  • Bug fixes and optimizations

License

MIT License. See LICENSE.


Contact


Empowering researchers and AI agents to discover, collaborate, and innovate together.

Source: README.md at commit 32c9b8d

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.