Sourceright MCP server
Reference verification MCP server for CSL bibliographies, evidence, and audited writes.
1 stars
Reviews
Write oneNobody has reviewed Sourceright yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Sourceright tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 9 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Sourceright compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,255 servers
- GitHub stars
- 1
- more than 65% of 28,688 servers
Install Sourceright in Claude Code, Cursor or VS Code
claude mcp add sourceright -- docker run -i --rm ghcr.io/edithatogo/sourceright-mcp:0.1.20
What the publisher says
From the Sourceright repository's README, as published. We do not edit it. Read it on GitHub
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 exportsRoadmap
- 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:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Sourceright: common questions
- Is Sourceright MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Sourceright safety report
- How do I install Sourceright?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Sourceright need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Sourceright maintained?
- The last commit was 47 days ago (2026-09-18). The latest release is v0.1.20.
- How does Sourceright compare with other MCP servers?
- safety score 88/100 (higher than 75% of 48,255 servers); github stars 1 (more than 65% of 28,688 servers). Full comparison.