WORKS Public Verifier

io.github.DYZCODE由 GitHub 帳號 DYZCODE 發布v0.1.13更新於 Oct 25, 2026

Independent static verification for exact immutable public GitHub commits.

已驗證Streamable HTTP可網頁執行開發者工具安全與監控

概覽

AI 產生的概覽

一個遠端 MCP 伺服器，對指定的公開 GitHub 提交做靜態驗證，依固定合約回傳簽章回執。

可以做什麼
在驗證前檢查儲存庫、提交參照與宣告是否符合資格，並為僅支援工具的用戶端提供預檢，對不合格輸入直接棄權（works_public_eligibility）。對已確認的公開儲存庫、精確的小寫 40 字元提交 SHA 與受支援的靜態宣告，回傳固定的合約摘要與範圍（works_public_contract_lint）。下載不可變的公開 GitHub 快照，在不執行儲存庫指令的前提下執行選定的固定靜態合約，並回傳簽章回執（works_verify_public_repository）。
適用情境
當你需要對某個公開 GitHub 提交做獨立、唯讀的靜態查核時適用，例如確認套件或環境安全方面的宣告，並希望取得簽章回執而非建置或測試結果。
執行需求
遠端 streamable HTTP 端點；未宣告驗證、環境變數或標頭。驗證對象必須是公開 GitHub 儲存庫中精確的小寫 40 字元提交 SHA，且僅支援 node-package 與 env-safety 兩種靜態合約。需要能連線至該端點的網路。
安裝前請注意
回執只證明其合約所宣告的結果，不證明建置、測試、部署、付款、執行時行為或市場驗證。README 稱驗證工具為唯讀，不儲存遙測、儲存庫網址、提交 SHA、原始碼、工具請求內容、憑證或安裝識別碼，回執僅回傳給呼叫方。可選的安裝器會送出一次無內容的彙總安裝訊號，可用 --no-signal 關閉。

安裝

在 SourceWeft 中

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

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.DYZCODE%2Fworks-public/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "works-public-verifier": {
      "type": "http",
      "url": "https://works-runner.vercel.app/mcp-registry"
    }
  }
}

README

WORKS Public Verifier

WORKS independently checks an immutable public GitHub commit against a pinned static contract and returns a signed receipt. The pilot never executes repository commands and supports only exact lowercase 40-character commit SHAs.

One-command install

Install in every detected supported agent without supplying a Vercel credential:

console
npx github:DYZCODE/works-plugins

Use --client codex or --client claude to select only one host. Restart the host after the installer completes.

After success, the installer sends one bodyless aggregate install signal. It contains no installation ID, account, repository, payload, or cookie and can be disabled with --no-signal.

Install in Codex

Add this repository as a marketplace:

console
codex plugin marketplace add DYZCODE/works-plugins --ref v0.1.13

Restart the ChatGPT desktop app, open Plugins, choose WORKS Plugins, and install WORKS Public Verifier.

Install in Claude Code

Add the same repository as a marketplace and install the plugin:

console
claude plugin marketplace add DYZCODE/[email protected]claude plugin install works-public@works-plugins

MCP Registry

The official MCP Registry metadata points to a dedicated three-tool endpoint. Its frozen Codex gate passed with 20 of 20 eligible verifications, zero verification in 20 ineligible controls, 100% eligible response fidelity, and no final host errors. Ineligible controls had a 34.8955-second median and a 67.353-second maximum final wall time. One control recovered on its single allowed retry.

The Registry is currently in preview. The Codex and Claude plugin path remains available so supported hosts can also install the strict selection and abstention skill.

The v0.1.6 Registry attempt was rejected before publication because its GitHub namespace casing did not match the OIDC grant. v0.1.7 published the correct Registry metadata but retained the previous Codex adapter version. v0.1.8 aligned the Codex, Claude, and Registry release metadata. v0.1.9 adds the one-command installer and its bodyless aggregate install signal without changing the validated verification tool or trust anchor. v0.1.10 makes the installer replace older tag-pinned marketplace snapshots before reinstalling. v0.1.11 publishes the fresh paired multistack result and adds a locked, testable installer package. v0.1.12 publishes the rejected v3 scale result and its successful targeted v4 corrective canary without changing the public static verifier or trust anchor. v0.1.13 publishes the passing reserved v4b holdout and advances only the technical evidence state; billing, the verifier, and the trust anchor are unchanged.

Pilot evidence

The frozen Codex gate passed with 20 of 20 eligible selections, zero activation in 20 ineligible controls, complete receipt fidelity, and a 0.5905-second median eligible-minus-control wall-time delta. One ineligible control recovered on its single allowed retry.

Claude marketplace and plugin manifests validate, but autonomous Claude selection was not executed for this release because the local test account required reauthentication. No cross-host claim is made.

The fresh repair-agent pilot then compared 20 randomized pairs across Node, Python, monolithic, and layered fixtures. WORKS passed 20/20 while the control passed 6/20, a 70-point lift. It stayed within the frozen wall-time and verifier call budgets; median input tokens increased by 53.24%. Raw results, score, hashes, method, and limitations are in evidence/.

The next frozen scale run stopped at 34 tasks with verdict kill_or_pivot. WORKS retained a 23.33-point success lift and neutral median wall time, but missed the 25% token limit at 26.44% and exhausted its final error budget. A targeted four-case corrective canary then passed 4/4 with 68.32% lower median input tokens and 67.08% lower median wall time than the corresponding v3 arms.

The reserved fresh v4b holdout then completed 23 decisive pairs. WORKS passed 21/23 while the same model without WORKS passed 7/23, a 60.87-point lift. Median wall time fell 45.01% and median input tokens fell 20.44%. All frozen runtime, fixture, verifier-call, selection, and error gates passed. One WORKS arm timed out, and two Python repairs failed in both arms. This clears the technical pilot gate; it does not prove organic routing, real-repository performance, retention, willingness to pay, or a durable moat.

Pilot scope

  • Plugin MCP endpoint: https://works-runner.vercel.app/mcp
  • Registry MCP endpoint: https://works-runner.vercel.app/mcp-registry
  • Trust anchor: https://works-runner.vercel.app/trust
  • Contracts: node-package and env-safety
  • Source: public GitHub repositories at immutable commits
  • Execution: static checks only

The automatic verification tool is read-only and stores no verification telemetry, repository URL, commit SHA, source, tool body, credentials, or installation identifier. Its signed receipt is returned to the caller only.

A passing static receipt proves only the outcomes declared by its contract. It does not prove builds, tests, deployments, payments, runtime behavior, or market validation.

來源：README.md，提交 35002c5

工具

3

works_public_eligibility

Check WORKS verification eligibility

Fast deterministic preflight for tool-only clients. Call this before any other WORKS tool when eligibility is uncertain, especially for mutable or abbreviated refs, local or private repositories, and build, test, runtime, deployment, or production claims. It does not download a repository or persist data. If eligible is false, stop without calling verification.

輸入參數claim必填referencesource_kind必填repository_urlrepository_visibility必填

works_public_contract_lint

Inspect public WORKS contract

After a task is already known to have a public GitHub repository, an exact lowercase 40-character commit SHA, and a matching supported static claim, return the pinned contract digest and scope. Do not call for mutable or abbreviated refs, local or private repositories, runtime, builds, tests, deployments, or broad production-readiness claims.

輸入參數contract必填

works_verify_public_repository

Verify immutable public repository

Use only after works_public_eligibility returns eligible. Download that immutable public GitHub snapshot, run the selected pinned static contract without executing repository commands, and return a signed receipt. Return the report field verbatim and stop.

輸入參數contract必填commit_sha必填repository_url必填

版本歷史

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

評分

已滿足適用檢查項的 100%

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

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分