WORKS Public Verifier
Overview
Description from the maker (original English)
Independent static verification for exact immutable public GitHub commits.
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Developer tools
Install
Pick the AI app you use, then copy the settings.
Passed 5/5 checks · What you ask goes through the maker’s server (works-runner.vercel.app)
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude · about 2 min
No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1
Open Claude’s Connectors page
CustomizeConnectors
Click “+ Add” → “Add custom connector” and fill in these 2 fields
Copy each value into the field with the same name in Claude, then click Continue
Name · NameWORKS Public VerifierRemote MCP server URL · Addresshttps://works-runner.vercel.app/mcp-registryLeave Authentication as Claude detected it, then click Add
Turn it on in a chat
+ConnectorsWORKS Public Verifier
Try it
Use WORKS Public Verifier and tell me what you can do for me, then show me one thing✓ If Claude says it is using WORKS Public Verifier or shows a WORKS Public Verifier tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with ChatGPT on business plans only
ChatGPT Business, Enterprise or Edu on the web, added by a workspace admin or owner · On Free, Plus or Pro: your ChatGPT plan cannot connect MCP yet
Open ChatGPT’s add-MCP page on the web
Plugins+Add custom MCP server
Fill in the name and address
Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin
Name · NameWORKS Public VerifierConnection · Addresshttps://works-runner.vercel.app/mcp-registryPick WORKS Public Verifier in a chat
Start a new chat and pick WORKS Public Verifier from your plugins before typing
Try it
Use WORKS Public Verifier and tell me what you can do for me, then show me one thing✓ If ChatGPT says it is using WORKS Public Verifier or shows a WORKS Public Verifier tool in the answer, you are connected
Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Claude Code · about 2 min
No key, nothing to install
Open Terminal
Mac: press Command+Space and type Terminal · Windows: open PowerShell
Paste this command and press Enter
claude mcp add --transport http works-public https://works-runner.vercel.app/mcp-registryType /mcp in Claude Code
You should see WORKS Public Verifier listed as connected
Try it
Use WORKS Public Verifier and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using WORKS Public Verifier or shows a WORKS Public Verifier tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor · about 2 min
No key, nothing to install
Open the AI chat in Cursor in Agent mode
Try it
Use WORKS Public Verifier and tell me what you can do for me, then show me one thing✓ If Cursor says it is using WORKS Public Verifier or shows a WORKS Public Verifier tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code · about 2 min
No key, nothing to install
Open the AI chat in VS Code in Agent mode
Try it
Use WORKS Public Verifier and tell me what you can do for me, then show me one thing✓ If VS Code says it is using WORKS Public Verifier or shows a WORKS Public Verifier tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
Address for apps that connect over the web
https://works-runner.vercel.app/mcp-registryJSON settings are under “For developers” below
For developers: Terminal commands and JSON settings
Over the web
Claude Code
claude mcp add --transport http works-public https://works-runner.vercel.app/mcp-registryCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"works-public": {
"url": "https://works-runner.vercel.app/mcp-registry"
}
}
}VS Code (mcp.json)
{
"servers": {
"works-public": {
"type": "http",
"url": "https://works-runner.vercel.app/mcp-registry"
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
At a glance
Which apps can use it
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
Related guides
What it can do
Tool names and descriptions exactly as the server reported them on Nov 10, 2026. The maker wrote them, not us; we show them as plain text.
works_public_eligibilityFast 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 r
works_public_contract_lintAfter 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, b
works_verify_public_repositoryUse 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.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 11, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account DYZCODE, which owns the repo
- ✓ Pass
Still maintained
Code last changed 4 months ago
- ✓ Pass
Has a licence
Uses MIT
- ✓ Pass
Endpoint responds
Responded in 139 ms (HTTP 200)
- – Not applicable
Sign-in with OAuth
No sign-in needed
- ✓ Pass
No hidden instructions in tool descriptions
Read 3 tool descriptions and found no hidden instructions to the AI
Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
User reviews
No reviews yet
Compared with others in Developer toolsi
- More stars than 0% of the other 5768 servers in this category
- Published to the registry more recently than 24% of the other 5768 servers in this category
- Basic checks equal to or better than 100% of the other 5768 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is WORKS Public Verifier safe?
It passed 5 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed 4 months ago, and the latest version (0.1.13) reached the registry 4 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT Business and above.
What can I use instead?
In the same category: REA, Netdata, Front-End Checklist
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Netdata
Real-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.
Front-End Checklist
Review frontend code and live pages against 386 quality-gated web development rules.
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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:
npx github:DYZCODE/works-pluginsUse --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.13Restart 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.13claude 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-packageandenv-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.