MCP registry

The server.json manifest in the public repository, what each field means, and where the server can be found today.

Registries and client installers read one file to learn how to reach an MCP server. Ours is server.json at the root of the public repository:

server.json

{
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-09-29/server.schema.json",
  "name": "dev.wellworn/mcp",
  "description": "Verified picks, traps at your version, skills, and design systems for coding agents. Works without a key.",
  "repository": { "url": "https://github.com/WellWorn-dev/wellworn", "source": "github" },
  "version": "0.1.0",
  "remotes": [{ "type": "streamable-http", "url": "https://mcp.wellworn.dev/mcp" }]
}

What the fields commit to

name is a reverse-DNS namespace plus a server name. The registry ties that namespace to how you authenticate: a dev.wellworn/* name can only be published by someone who proves control of wellworn.dev through a DNS TXT record on the apex, and an io.github.* name by the GitHub account it matches. The name is not a URL and clients do not resolve it.

Verified 2026-09-08 against github.com

remotes is the part a client acts on. One entry, streamable-http, pointing at https://mcp.wellworn.dev/mcp: the same endpoint every client page in these docs configures, and the same one the Claude Code plugin ships in its .mcp.json. There is no packages array because there is nothing to install; the server is hosted, stateless, and answers without a key. A remote server has to be publicly reachable at the URL it publishes, which this one is.

version describes the server, not the corpus. New verdicts and new traps reach every client the moment a reviewer publishes them, with no manifest change and nothing for you to update.

Verified 2026-09-08 against github.com

Where the server is listed

The official MCP registry does not carry dev.wellworn/mcp yet. Until it does, add the server the way your client page describes, or hand the manifest to any tool that reads a server.json. Nothing about the endpoint depends on a listing: it is the same URL either way.

Verified 2026-09-08 against registry.modelcontextprotocol.io

Publishing a copy

If you run your own build of the server, publish it under your own namespace rather than reusing ours: copy server.json, change name to your domain in reverse-DNS form or io.github.<you>/<server>, point remotes[0].url at your deployment, then install the mcp-publisher CLI and run mcp-publisher login dns --domain=<yours> --private-key=<hex> (or login github) followed by mcp-publisher publish. mcp-publisher validate checks the file without publishing anything. The registry is in preview and can reset its data, so treat a listing as discovery, not as infrastructure.

Verified 2026-09-08 against github.com