Sourceright

Name: Sourceright
Author: edithatogo

作者：edithatogo版本 0.1.20i★ –i在你的电脑上运行

注册名称io.github.edithatogo/sourceright

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你需要

Docker已安装 Docker

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

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

在终端中运行这条命令

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

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 edithatogo 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 18334 个服务器的 0%
发布到注册中心的时间比此分类中其他 18334 个服务器的 7% 更新
基础检查结果等于或优于此分类中其他 18334 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Sourceright 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.1.20）于6个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Docker。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, ProAgentStore

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

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

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

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

在云端运行★ 211前天更新

安装

ProAgentStore

作者：ProAgentStore

MCP-first control plane for ProAgentStore agents and private instances.

在云端运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“其他”中的其他服务器比较i

常见问题

替代选择

Spec Driven Development

Remote Desktop Commander

ProAgentStore

作者的 README

Sourceright

Who This Is For

What It Does / Does Not Do

Workflow

Roadmap

Current Status

CLI

Planned Distribution

Distribution metadata files

Development

License