Research Scope

io.github.AxelVerneBooksPublished by GitHub account AxelVerneBooksv0.1.2Updated Oct 24, 2026

Plan research, score sources for freshness/COI, and enforce claim-level citations in reports.

The publisher's own server: Scope (AEC) - Preview

Overview

AI-generated overview

A local MCP server that plans research, scores sources for quality and freshness, and builds reports with enforced claim-level citations.

What you can do
Plan research: turn a scope into a source-target plan with kill criteria for thin evidence, optionally guided by domain hints. Fetch and score sources: crawl one URL and return an explainable 0–100 quality score with flags for primary status, freshness, paywall and conflict of interest. Build reports: assemble a citation-registry report shell with numbered citations and a scoring appendix from already-scored sources. Check reports: verify every substantive claim cites at least one scored source and return orphan claims as an error list.
When to use it
Useful when an assistant writes research reports that must show where each claim came from, or when you want source quality scored and citation coverage checked mechanically before a report is trusted.
Requirements
Runs as a local process over stdio, typically launched with npx; a Streamable HTTP mode with a port option is also documented. Node.js is needed for the npm package, and network access is required to fetch and score sources. No accounts, API keys or environment variables are declared.
Before you install
Fetching a source URL makes outbound network requests to third-party sites. Reports are written under a local data directory, and the check step can fail a report rather than approve it. The README mentions a paid kit built around this free core, so expect promotion of paid material.

Installation

In SourceWeft

  1. Open Research Scope 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

research-scope-mcp

Turn a scattered source set into a decision-ready, traceable report.

research-scope-mcp is an MCP server that runs a research-to-report workflow any MCP client can drive end to end:

  1. plan_research(scope) — turns a research scope into a source-target plan with kill criteria ("fewer than 1 primary + 2 independent secondaries → stop and report insufficient sources, don't proceed on thin evidence").
  2. fetch_and_score(source_url) — crawls one source and returns an explainable 0–100 quality score: primary-source detection, publication freshness, paywall and conflict-of-interest flags — every dimension returned with the evidence.
  3. build_report(topic, sources) — assembles a citation-registry report shell (claims section + numbered registry + scoring appendix) for the scored sources.
  4. check_report(report) — verifies every substantive claim cites ≥1 scored source. Orphan claims come back as an error list, not a pass.

The problem it solves: agent-written reports that sound confident but can't show where any sentence came from. This server makes scoring and citation coverage mechanically enforced, so the report is auditable by a human in 90 seconds.

Install

bash
npm install -g research-scope-mcp   # once published; local: npm ci && npm run build

Run over stdio (most clients):

bash
npx research-scope-mcp

Or over Streamable HTTP (remote deployments):

bash
npx research-scope-mcp --http --port 3001# unauthenticated requests get 401 + WWW-Authenticate discovery, never a bare 403

Client config

Drop-in config snippets for Claude Code, Cursor, and a Cline-friendly llms-install.md.

Docker

bash
docker build -t research-scope-mcp -f docker/Dockerfile .docker run --rm -i -p 3001:3001 research-scope-mcp --http --port 3001

Tools

ToolInputOutput
plan_researchscope, optional domain_hintssource-target plan with kill criteria
fetch_and_scoresource_url0–100 score + flags (primary, freshness, paywall, COI), registered for reporting
build_reporttopic, sources[] (must already be scored)report shell saved under data/reports/, [Sn] citation numbering
check_reportreport_id or report_pathpass/fail + orphan-claim error list

Example walkthrough

See docs/runs/ for two worked runs with inputs and outputs, and docs/notes/ for what to do when something times out or 401s.

Demo capture

npm run demo:capture (or node tools/demo-capture.mjs) replays the scripted 60-second demo flow against the shipped server — spawn dist/index.js over stdio with a fresh temp data dir, plan_research → fetch_and_score a .gov page (real fetch) → build_report, inject one cited claim plus one deliberately orphan claim, and confirm check_report refuses to bless it — writing each frame out as a {t, dir, msg} JSONL transcript. By default it targets docs/marketing/demo-60s/run-capture.jsonl (the transcript the product-page demo player's footer sha256 is anchored to); it refuses to overwrite that file without --force. Requires network access for the one real fetch; repo data/ is never touched.

Scoring rubric

DimensionMaxNotes
Availability & substance20extractable text length
Primary-source status32host class (gov/edu/filings) or self-published primary (press/announcement paths)
Freshness24≤30d full marks, decays to 2 at >5y, 0 if undetectable
Access12paywall/registration walls lose marks
Independence12sponsored/affiliate/partnership markers

score ≥ 80 → A, ≥ 65 → B, ≥ 45 → C, else D. The rubric is inside src/scoring/score.ts and returns its evidence, so a score is auditable, not a vibe.

License

MIT. See SECURITY.md for reporting security issues.

Paid kit

This server is the free, tested core of the Research-to-Report MCP Kit (field guide, worked example packs, setup support). Available at the kit store — link in CHANGELOG.md updates.

Source: README.md at commit d574931

Tools

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

Version history

2
  1. v0.1.2LatestOct 17, 2026
  2. v0.1.0Oct 16, 2026

Score

50% 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

Other Scope integrations