Sourceright

io.github.edithatogo由 GitHub 帳號 edithatogo 發布v0.1.20更新於 Oct 24, 2026

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

已驗證STDIO僅桌面知識與記憶開發者工具

概覽

AI 產生的概覽

一個技術預覽版 MCP 伺服器,用於擷取、清理、核驗並匯出 CSL 參考文獻,並附帶可稽核的證據旁檔。

可以做什麼
從文件或文字中擷取參考文獻與文內引用,轉換為標準 CSL JSON,支援直接解析 DOCX,並可驗證 CSL、產生報告,在缺少或損壞核驗旁檔時給出降級涵蓋診斷。對紀錄進行標準化、清理、核驗與補充,蒐集提供者證據,並把不確定條目送入人工複核佇列。解決衝突、協調引用並產生參考文獻完整性報告。匯出 XML、ENW、RIS、BibLaTeX 和 YAML 等乾淨參考文獻檔案,供 EndNote、Zotero、BibLaTeX 等工具使用。執行不依賴即時提供者的確定性基準測試,並可預覽或套用 citation-sync 寫入。
適用情境
適合需要可稽核、確定性引用清理與以 CSL 為中心的文獻流程的技術編輯、研究誠信與圖書館團隊,以及開發者或代理工作流程。它是供評估與試辦的技術預覽,不能取代審查員等級的最終核驗。
執行需求
以本機 stdio 程序在桌面執行,以 OCI 映像(ghcr.io/edithatogo/sourceright-mcp)散布。未宣告驗證、環境變數或請求標頭。README 描述了一個帶 mcp 子指令的 Rust 命令列工具,並計畫透過 GitHub Releases、crates.io 等管道散布。
安裝前請注意
專案自稱技術預覽,並非生產就緒產品或法庭提交合規系統;PDF 擷取、即時核心提供者檢查、URL/封存完整性、回寫建議等能力仍在強化中。citation-sync 僅在明確的 apply 旗標下寫入稽核日誌或遠端測試快照,建議先預覽。蒐集提供者證據時可能將參考文獻資料傳送給外部提供者。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Sourceright,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

Sourceright

[Release] [Publish crate] [Coverage] [smithery badge]

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

text
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:

powershell
pwsh -NoProfile -ExecutionPolicy Bypass -File scripts/run-local-rust-gates.ps1pwsh -NoProfile -ExecutionPolicy Bypass -File scripts/check-workflow-harness.ps1pwsh -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

text
sourceright init [document-or-directory]sourceright validate-csl [--json] <references.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

powershell
cargo checkcargo testcargo fmt --checkcargo clippy --all-targets -- -D warningscargo run --bin sourceright -- benchcargo package --lockedcargo publish --dry-run --lockedcargo machetecargo semver-checks check-release --release-type minor  # advisory until the public Rust API is stabilizedcargo deny check advisories bans sourcescargo tree -d --lockedtaplo lint Cargo.toml book.toml deny.toml lychee.toml rust-toolchain.toml taplo.toml typos.toml fuzz/Cargo.toml plugins/**/*.toml .cargo/config.tomltypos --config typos.tomlnpm --prefix docs-site run typecheckvale --minAlertLevel=error README.md docs/src docs/import-manifest.md .github/copilot-instructions.mdnpx --yes [email protected] README.md "docs/**/*.md" ".github/**/*.md"lychee --config lychee.toml --offline README.md docs/src/**/*.md docs/import-manifest.mdactionlintzizmor --min-severity medium .github/workflowscargo llvm-cov --locked --all-targets --fail-under-lines 85cargo mutants --workspacepwsh -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.

來源:README.md,提交 c5fa583

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v0.1.20最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分