Sourceright

Name: Sourceright
Author: edithatogo

by edithatogoversion 0.1.20i★ –iRuns on your computer

Registry nameio.github.edithatogo/sourceright

Install

Overview

Description from the maker (original English)

Reference verification MCP server for CSL bibliographies, evidence, and audited writes.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

DockerDocker installed

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "sourceright": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/edithatogo/sourceright-mcp:0.1.20"
      ]
    }
  }
}

Run this in your terminal

claude mcp add sourceright -- docker run -i --rm ghcr.io/edithatogo/sourceright-mcp:0.1.20

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "sourceright": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/edithatogo/sourceright-mcp:0.1.20"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "sourceright": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/edithatogo/sourceright-mcp:0.1.20"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account edithatogo, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 18329 servers in this category
Published to the registry more recently than 7% of the other 18329 servers in this category
Basic checks equal to or better than 100% of the other 18329 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Sourceright safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.20) reached the registry 6 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Excaliself

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

Excaliself

by maciekzygmunt

Find, read, create, edit, and organize Excalidraw drawings in your self-hosted Excaliself instance.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Sourceright

Sourceright is Rust-first reference triage and verification infrastructure for academic writing, agent workflows, and future legal citation work. It is currently a technical preview suitable for developer evaluation and pilot conversations.

Who This Is For

Technical editors and research-integrity teams that need auditable reference cleanup.
Library, repository, and publisher teams that want deterministic citation verification workflows.
Developers and agent workflows that need CSL-centered bibliographic pipelines with sidecar evidence.
Legal-tech researchers evaluating a separate legal citation path without conflating it with academic CSL.

What It Does / Does Not Do

Sourceright takes references from documents or text, produces canonical CSL JSON, standardises and cleans the records, collects provider evidence, routes uncertain records to manual review, and exports clean reference files for tools such as EndNote, Zotero, and BibLaTeX.

It does not claim to be a production-ready institutional product, a court filing compliance system, or a substitute for examiner-grade final verification. DOCX manuscripts are now parsed directly for citation intake, but broader PDF extraction, live core-provider checks, better citation disambiguation, URL/archive integrity, and low-noise writeback suggestions remain hardening tracks.

Workflow

document/text

-> extracted references and in-text citations -> references.csl.json -> standardisation, cleaning, verification, enrichment -> references.verification.json and review-queue.jsonl -> conflict resolution, citation reconciliation, and reference integrity reports -> XML, ENW, RIS, BibLaTeX, and YAML exports

Roadmap

Academic reference extraction and CSL JSON canonicalisation.
Provider-backed verification through Crossref first, then DOI resolution, DataCite, OpenAlex, PubMed/NCBI, and ORCID where useful.
In-text citation reconciliation against reference-list entries.
Manual review queues designed for human and agent/subagent verification.
Platform-neutral journal screening outputs for editorial workflows, with OJS as the first public integration target.
Reference reports for citation integrity auditing and AI-related citation-error signals.
CLI and MCP server interfaces over the same Rust core.
Legal citation analysis with a separate legal citation model and public-provider slots.
Claim/source/provenance graphs built over detected citation support without asserting claim truth.
Examiner-grade audit hardening for broader PDF extraction, live provider evidence, institutional-author matching, URL/archive checks, and explicit writeback plans.

See conductor/tracks.md for the implementation track map. The canonical requirements and repo contract are in docs/src/feature-contract-matrix.md, with the design diagrams in docs/src/design.md.

The current quality and security contract is documented in docs/src/security-and-quality-gates.md. Use the repository's bounded local gate runner before opening a change:

pwsh -NoProfile -ExecutionPolicy Bypass -File scripts/run-local-rust-gates.ps1

pwsh -NoProfile -ExecutionPolicy Bypass -File scripts/check-workflow-harness.ps1 pwsh -NoProfile -ExecutionPolicy Bypass -File scripts/check-release-parity.ps1

On Linux or macOS, the Rust gate runner is also available as ./scripts/run-local-rust-gates.sh. It uses the host stable toolchain and a temporary target directory; the PowerShell runner follows the same policy and selects the Windows GNU toolchain only when GCC is available.

Current Status

The Rust core now includes canonical CSL handling, verification sidecars, intake segmentation, provider evidence normalization, cleaning, conflict resolution, citation reconciliation, manual review queues, reporting, exports, journal screening contracts, legal citation records, and claim/source provenance graphs. It should be treated as a structured triage and audit workflow and technical preview while the active Conductor programme hardens extraction, interoperability, publication trials, and external registry acceptance. Imported reference workflow material lives under legacy/humanizer-next/ as provenance and regression material until audited, ported, or retired.

CLI

sourceright init [document-or-directory]

sourceright validate-csl [--json] sourceright report [--json|--mcp-resource] [.sourceright-directory] sourceright export --preview --all [.sourceright-directory] sourceright bench [--json] sourceright citation-sync [--preview|--apply] [.sourceright-directory] sourceright mcp

bench runs the checked-in fixture suite without live providers. The benchmark surface is a technical preview for deterministic regression and stress checks. citation-sync defaults to preview mode and requires explicit --apply before writing audit logs or remote fixture snapshots.

report can operate on a CSL-only directory. It emits a degraded-coverage diagnostic when references.verification.json is absent, while malformed sidecars fail with the path and a repair action instead of exposing only a low-level parser error.

Planned Distribution

sourceright CLI binary.
sourceright mcp server mode.
GitHub Releases with platform binaries, checksums, and provenance artifacts.
crates.io package after release dry runs pass.
OCI MCP image metadata for the official MCP Registry via server.json + Dockerfile labels.
Smithery readiness for the local stdio/MCPB path; hosted HTTP transport remains deferred.
Glama ownership metadata via glama.json.
release-status.md artifacts from the release and tag-triggered publish workflows.
coverage-status.md artifacts from the scheduled coverage workflow.
Thin adapter packages only where native tool ecosystems require them.
The active hardening programme is recorded in conductor/tracks.md; it includes harness/security/quality CI, interoperability fixtures, extraction experiments, and open-publishing platform trials.
Older track numbers remain in the Conductor archive for historical traceability; they are not a current product-readiness claim.
Tracks 36-40 cover examiner-grade audit hardening: document extraction, live core providers, citation disambiguation, URL/archive integrity, and low-noise writeback suggestions.
See docs/src/release-runbook.md, docs/src/coverage-reporting.md, and docs/src/docs-cutover.md for the operational sequence behind those tracks.
v*.*.* tags now auto-start the crate publish workflow, and the MCP registry workflow follows the release workflow completion.

Distribution metadata files

server.json (io.github.edithatogo/sourceright)
Dockerfile labels:
io.modelcontextprotocol.server.name
org.opencontainers.image.source
glama.json

Registry listings are external operational surfaces. Their current state and remaining maintainer or platform blockers are recorded in conductor/submission-packets/live-evidence.json; repository metadata alone is not treated as proof of a live score or callable-tool listing.

Development

cargo check

cargo test cargo fmt --check cargo clippy --all-targets -- -D warnings cargo run --bin sourceright -- bench cargo package --locked cargo publish --dry-run --locked cargo machete cargo semver-checks check-release --release-type minor # advisory until the public Rust API is stabilized cargo deny check advisories bans sources cargo tree -d --locked taplo lint Cargo.toml book.toml deny.toml lychee.toml rust-toolchain.toml taplo.toml typos.toml fuzz/Cargo.toml plugins/**/*.toml .cargo/config.toml typos --config typos.toml npm --prefix docs-site run typecheck vale --minAlertLevel=error README.md docs/src docs/import-manifest.md .github/copilot-instructions.md npx --yes markdownlint-cli2@0.18.1 README.md "docs/**/*.md" ".github/**/*.md" lychee --config lychee.toml --offline README.md docs/src/**/*.md docs/import-manifest.md actionlint zizmor --min-severity medium .github/workflows cargo llvm-cov --locked --all-targets --fail-under-lines 85 cargo mutants --workspace pwsh -NoProfile -ExecutionPolicy Bypass -File scripts/verify.ps1 -CoverageMinimum 85

Coverage stays gated above 85 percent line coverage in CI and in the checked-in pre-commit hook.

Release and publish workflows each emit a release-status.md artifact so the latest tag has a named checklist surface. Coverage runs emit a coverage-status.md artifact so the latest numeric report has a named checklist surface.

License

Licensed under either of:

Apache License, Version 2.0
MIT license

at your option.

Sourceright

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Excaliself

README from the maker

Sourceright

Who This Is For

What It Does / Does Not Do

Workflow

Roadmap

Current Status

CLI

Planned Distribution

Distribution metadata files

Development

License