io.github.DYZCODE/works-public
OfficialProvides verification of public GitHub commits against static contracts, returning signed receipts.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@io.github.DYZCODE/works-publicVerify commit 0123456789abcdef0123456789abcdef01234567 against node-package"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
Related MCP server: attest-mcp-remote
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.13
claude plugin install works-public@works-pluginsMCP 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/mcpRegistry MCP endpoint:
https://works-runner.vercel.app/mcp-registryTrust anchor:
https://works-runner.vercel.app/trustContracts:
node-packageandenv-safetySource: 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.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseAqualityAmaintenanceRead-only MCP server for precise lookup, search, and versioned retrieval of OWASP testing guides (WSTG, MASTG, ISTG, AITG) with full provenance on every result.Last updated11Apache 2.0
- Alicense-qualityBmaintenanceMCP server for verifying and attesting SHA-256 fingerprints of digital works via Streamable HTTP, with zero-install and privacy-preserving design.Last updatedMIT
- AlicenseAqualityAmaintenanceRead-only MCP server that exposes the agentic-os governance, SDLC, and Quality Engineering methodology to any MCP host. It never writes to your repository and never executes code — it serves the methodology, plans an install, and verifies it, handing any commands back to the host to run.Last updated27Apache 2.0
- Alicense-qualityCmaintenanceA read-only MCP server for operator-grade release inspection and benchmark browsing.Last updated61MIT
Related MCP Connectors
Read-only Remote MCP for externally grounded AI agent trust receipts.
A paid remote MCP for ZeroID, built to return verdicts, receipts, usage logs, and audit-ready JSON.
A paid remote MCP for hosted MCP server, built to return verdicts, receipts, usage logs, and audit-r
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/DYZCODE/works-plugins'
If you have feedback or need assistance with the MCP directory API, please join our Discord server