MCP.Market

WORKS Public Verifier MCP server

online · 100% uptime
by DYZCODE·io.github.DYZCODE/works-public·v0.1.13

Independent static verification for exact immutable public GitHub commits.

B84/100grade B
What users say
No reviews yet
Be the first
Safety scan
B84/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed WORKS Public Verifier yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

WORKS Public Verifier tools (3)

write = sends, deletes, buys or posts
  • works_public_contract_lintFree

    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.

  • works_public_eligibilityFree

    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.

  • works_verify_public_repositoryFree

    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.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 380ms20/20
  • Tool poisoning3 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 60 days ago12/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 84/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How WORKS Public Verifier compares

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
84/100
higher than 68% of 1,119 Developer tools servers
Tools
3
the typical Developer tools server has 7
Tools that change things
0%
typical: 5%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote Developer tools server answers 100%
Response time
71 ms
faster than 80% of 443 Developer tools servers

What its tools let an agent do: 3 read

Install WORKS Public Verifier in Claude Code, Cursor or VS Code

claude mcp add --transport http works-public https://works-runner.vercel.app/mcp-registry
Add to Cursor

What the publisher says

From the WORKS Public Verifier repository's README, as published. We do not edit it. Read it on GitHub

WORKS Public Verifier

<!-- mcp-name: io.github.DYZCODE/works-public -->

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:

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:

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:

claude plugin marketplace add DYZCODE/works-plugins@v0.1.13
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/.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

WORKS Public Verifier: common questions

Is WORKS Public Verifier MCP server safe?
Mostly: it is graded B (84/100). Read the WORKS Public Verifier safety report
How do I install WORKS Public Verifier?
It runs remotely at works-runner.vercel.app. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does WORKS Public Verifier need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is WORKS Public Verifier maintained?
The last commit was 100 days ago (2026-07-27). The latest release is v0.1.13.
Is WORKS Public Verifier up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of WORKS Public Verifier?
Servers from other publishers that do the same job: GitDiagram MCP server, OctoCounts MCP Server and GitHub MCP server.
How does WORKS Public Verifier compare with other Developer tools MCP servers?
safety score 84/100 (higher than 68% of 1,119 Developer tools servers); tools 3 (the typical Developer tools server has 7); tools that change things 0% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to WORKS Public Verifier

Same job from other publishers: the closest match first, then the best rated.

  • GitDiagram
    Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
    A
  • OctoCounts MCP Server
    Analyze and compare public GitHub repo line counts (SLOC) via OctoCounts, from any MCP client.
    A
  • GitHub
    Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
    A
  • Gk CLI
    The GitKraken MCP Server for managing repos, PRs, issues across GitHub, GitLab, Bitbucket and more.
    B
  • Agent Harnesses
    Agent-harness picks, decision guides, setup templates, and skills; live GitHub/HN discovery.
    A