WORKS Public Verifier
REMOTE · WORKS-RUNNER.VERCEL.APP · SCANNED SEP 20
Independent static verification for exact immutable public GitHub commits.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 421 tokens (~140/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 56% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the WORKS Public Verifier MCP server?
WORKS Public Verifier is a hosted endpoint at https://works-runner.vercel.app/mcp-registry, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · works-runner.vercel.app
claude mcp add --transport http dyzcode-works-public 'https://works-runner.vercel.app/mcp-registry'
{
"mcpServers": {
"dyzcode-works-public": {
"url": "https://works-runner.vercel.app/mcp-registry"
}
}
} {
"servers": {
"dyzcode-works-public": {
"type": "http",
"url": "https://works-runner.vercel.app/mcp-registry"
}
}
} [mcp_servers.dyzcode-works-public] url = "https://works-runner.vercel.app/mcp-registry"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dyzcode-works-public": {
"type": "remote",
"url": "https://works-runner.vercel.app/mcp-registry",
"enabled": true
}
}
} openclaw mcp add dyzcode-works-public --url 'https://works-runner.vercel.app/mcp-registry' --transport streamable-http
mcp_servers:
dyzcode-works-public:
url: "https://works-runner.vercel.app/mcp-registry" {
"McpServers": {
"dyzcode-works-public": {
"Transport": "http",
"Url": "https://works-runner.vercel.app/mcp-registry"
}
}
} assistant mcp add dyzcode-works-public -t streamable-http -u 'https://works-runner.vercel.app/mcp-registry'
{
"mcpServers": {
"dyzcode-works-public": {
"type": "http",
"url": "https://works-runner.vercel.app/mcp-registry"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- Stability: unverified → 0.03 ▲ functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- Server version: 0.1.6 → 0.1.7 functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://works-runner.vercel.app/mcp-registry
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 29 Aug 2026 | 27 Nov 2026 | RSA 2048 | SHA256-RSA | f7911168ffa7d0f4135e24792e7a52a8 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of works-runner.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://works-runner.vercel.app/mcp-registry | Verified | 200 | |
| http (plaintext) | http://works-runner.vercel.app/mcp-registry | HTTPS enforced | 308 | https://works-runner.vercel.app/mcp-registry |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
works_public_contract_lint Inspect public WORKS contract ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contract | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | – |
| digest | string | yes | – |
| execution | string | yes | – |
| id | string | yes | – |
| title | string | yes | – |
| trust | string | yes | – |
| valid | boolean | yes | – |
No examples provided.
works_public_eligibility Check WORKS verification eligibility ~193
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.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | Use static-evidence for generic signed or static repository evidence; it maps conservatively to node-package. Never use it for build, tests, runtime, deployment, or production claims. |
| reference | string | – | Reference exactly as supplied; never expand a branch, tag, or short SHA. |
| repository_url | string | – | Exact repository URL supplied by the user, if any. |
| repository_visibility | string | yes | Use public only when the request identifies a public repository. |
| source_kind | string | yes | Classify where the requested source lives. |
| Name | Type | Req | Description |
|---|---|---|---|
| contract | – | yes | – |
| eligible | boolean | yes | – |
| next_tool | – | yes | – |
| reason | string | yes | – |
| report | string | yes | – |
No examples provided.
works_verify_public_repository Verify immutable public repository ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| commit_sha | string | yes | – |
| contract | string | yes | – |
| repository_url | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| contract | object | yes | – |
| limitations | array | yes | – |
| outcomes | array | yes | – |
| receipt | object | yes | – |
| report | string | yes | – |
| source | object | yes | – |
| status | string | yes | – |
| trust | object | yes | – |
No examples provided.
What is the WORKS Public Verifier MCP server?
WORKS Public Verifier is an MCP server listed in the public MCP registry as io.github.DYZCODE/works-public. Independent static verification for exact immutable public GitHub commits. This page covers its hosted endpoint (https://works-runner.vercel.app/mcp-registry).
Is the WORKS Public Verifier MCP server safe to use?
WORKS Public Verifier scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the WORKS Public Verifier MCP server expose?
WORKS Public Verifier exposes 3 tools: works_public_eligibility, works_public_contract_lint, works_verify_public_repository. Their descriptions and schemas cost roughly 356 tokens of context every time the server is loaded.
Does the WORKS Public Verifier MCP server require authentication?
No. We connected to WORKS Public Verifier without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the WORKS Public Verifier MCP server still maintained?
WORKS Public Verifier is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.