WORKS Public Verifier MCP server
io.github.DYZCODE/works-publicDYZCODEstreamable-httpv0.1.13Scanned
Independent static verification for exact immutable public GitHub commits.
3 tools: 3 change things.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the WORKS Public Verifier MCP server can do
The WORKS Public Verifier MCP server is published by the GitHub account DYZCODE. It has 3 tools. It can create or change data (3 tools: works_public_eligibility, works_public_contract_lint and works_verify_public_repository), but cannot delete data. None of its tools only reads.
1 tool brings in text other people can write (works_verify_public_repository).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 15, 2026, version 0.1.13.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 3Claude Code: ask
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 dige…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
works_public_eligibilityFast deterministic preflight for tool-only clients.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
works_verify_public_repositoryUse only after works_public_eligibility returns eligible.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:57 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://works-runner.vercel.app/mcp-registry: tools/list returned 3 tools to an anonymous client, including works_public_eligibility (write), works_public_contract_lint (write), works_verify_public_repository (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.13. Values in angle brackets are yours to fill in.
claude mcp add --transport http works-public https://works-runner.vercel.app/mcp-registryclaude mcp add --transport http works-public https://works-runner.vercel.app/mcp-registryRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__works-public__works_public_eligibility",
"mcp__works-public__works_public_contract_lint",
"mcp__works-public__works_verify_public_repository"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as works-public. Review it before you use it.
Capability tags behind 1 rule
- mcp__works-public__works_verify_public_repository untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.DYZCODE/works-public/verify?hash=aea574edb92b0e329282424b2a81e82556e753f22443389e24b366469e82ada9" | jq -e '.changed == false'Pinned hash aea574edb92b, from Nov 15, 2026, 18:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.DYZCODE/works-public/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.DYZCODE/works-public)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:15 UTC.
WORKS Public Verifier MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the WORKS Public Verifier MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the WORKS Public Verifier MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the WORKS Public Verifier MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the WORKS Public Verifier MCP server have?
- 3 tools: 3 write. works_public_eligibility, works_public_contract_lint and works_verify_public_repository.
Does the WORKS Public Verifier MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the WORKS Public Verifier MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the WORKS Public Verifier MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.