# Sourceright [Health: Active]

**Category:** 🔬 Research  
**Repository:** https://github.com/edithatogo/sourceright  
**GitHub Stars:** 1  
**npm Downloads (last month):** 6954868  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/sourceright

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

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "sourceright": {
    "command": "npx",
    "args": ["--yes","markdownlint-cli2@0.18.1"]
  }
}
```

## Documentation

## What Sourceright MCP server does

Sourceright MCP server supports a structured workflow for cleaning and checking academic references. It accepts references from text or documents, including direct DOCX citation intake, and converts them into canonical CSL JSON. The workflow can standardize bibliographic records, collect evidence, identify conflicts, and place uncertain items into a manual review queue.

The resulting workspace can include a verification sidecar, review records, citation-integrity reports, and exports for downstream reference-management or publishing tools. Supported export formats include XML, ENW, RIS, BibLaTeX, and YAML. The project also includes records and contracts for journal screening, legal citation work, and claim/source provenance graphs, but the README presents these areas as part of a broader technical-preview workflow rather than a production compliance product.

## How it works

The processing path begins with document or text intake and extracted references or in-text citations. Sourceright then creates a `references.csl.json` file before applying standardization, cleaning, verification, and enrichment. Conflict resolution and citation reconciliation follow, producing audit-oriented reports and export files.

Provider-backed verification is being developed around Crossref first, with additional planned or useful provider paths including DOI resolution, DataCite, OpenAlex, PubMed/NCBI, and ORCID. The repository states that live core-provider checks and several other verification areas are still hardening tracks, so users should distinguish deterministic local processing from externally verified evidence.

The MCP interface is exposed through the `sourceright mcp` command and shares the Rust core with the CLI. Other commands support initialization, CSL validation, reporting, export previews, benchmarking, and citation synchronization. Citation synchronization defaults to preview mode and requires an explicit apply action before writing audit logs or remote fixture snapshots.

## Setup and configuration

Run the released or locally built `sourceright` binary in MCP mode with `sourceright mcp`. The repository also documents a local development path using Cargo, including `cargo check`, `cargo test`, formatting, linting, and package checks. No environment variables are documented as required for running the server.

A workspace can be initialized from a document or directory with `sourceright init [document-or-directory]`. Reports can operate on a CSL-only directory, but missing verification sidecars produce a degraded-coverage diagnostic. Malformed sidecars fail with a file path and repair guidance.

## Tools and capabilities

The Sourceright MCP server is suited to workflows that need:

- CSL JSON canonicalization and validation.
- Reference cleaning, normalization, and evidence sidecars.
- Manual review queues for uncertain records.
- In-text citation reconciliation.
- Reference integrity and audit reporting.
- Previewable exports to XML, ENW, RIS, BibLaTeX, and YAML.
- Deterministic benchmark runs using checked-in fixtures without live providers.

## Limitations and notes

The project is explicitly a technical preview for developer evaluation and pilot work. It is not presented as a production institutional system, a court-filing compliance service, or a replacement for final examiner-grade verification. Broader PDF extraction, live provider evidence, citation disambiguation, URL and archive checks, institutional-author matching, and low-noise writeback suggestions remain hardening work.

The Sourceright MCP server should therefore be used for structured triage, audit preparation, and reference-pipeline development. Its reports and evidence records can organize verification work, but they should not be treated as proof that every citation is correct or that a manuscript satisfies an external compliance requirement.

_Full upstream README: https://allmcps.com/mcp/sourceright/readme_