Developer · Remote MCP server

WORKS Public Verifier

Independent static verification for exact immutable public GitHub commits.

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.DYZCODE/works-public
Version
0.1.13
Status
Active
Category
developer
Transport
Streamable HTTP
Published
2026-07-27
Updated
2026-07-27
Publisher
DYZCODE (GitHub)
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/DYZCODE) · how
Listed under
GitHub MCP servers
Repository
github.com/DYZCODE/works-plugins
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://works-runner.vercel.app/mcp-registryNone

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 200)
Handshake
works-public 0.1.7 · protocol 2025-06-18
Tools discovered
3: works_public_eligibility, works_public_contract_lint, works_verify_public_repository
Checked on
2026-10-05

How the live check works

How to connect WORKS Public Verifier

WORKS Public Verifier is a remote MCP server: there is nothing to install. Its endpoint is https://works-runner.vercel.app/mcp-registry, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
Workflows MCP ServerStore, query, and create YAML workflow playbooks for LLM agents.Local · stdio, HTTPnpm: @cyanheads/workflows-mcp-server
WorkflowyCreate, update, complete nodes, search & replace with regex and dry run, usage reports, transforms.Local · stdioOCI image (Docker): ghcr.io/mholzen/workflowy:0.8.1
WorkingMemoryPersistent personal memory for AI assistants - save, search, and recall across every MCP client.Remote · HTTPLive check: ✓ handshakeapp.workingmemory.ai
WORKMINEX402 pay-per-call APIs over MCP, settled in USDC on Base for autonomous agents and developers.Remote · HTTPLive check: ✓ handshakeworkmine-mcp.onrender.com
Workspace ToolsSandbox workspace tools: search, file read, DB queries, integrations. Returns synthetic data.Remote · HTTPLive check: ✗ no handshakevandorla.com
Workspace ToolsResearch honeypot. Logs connections and tool arguments; injects instructions. Read README first.Remote · HTTPLive check: ✗ no handshakevandorla.com
WorkspaceguardWraps the WorkspaceGuard CLI as a single generic MCP tool for workspace usage checks.Local · stdioPyPI: workspaceguard-cli
Worktree Orbit MCPAggregate local Git worktree topology without exposing repository content. Tools include inspect...Local · stdionpm: worktree-orbit-mcp