Novaquill

Blog · 2026-11-18

Publish a remote MCP server to the official MCP Registry without GitHub (DNS auth)

The official MCP Registry (registry.modelcontextprotocol.io) accepts servers under two kinds of namespace: io.github.<user>/…, proven with a GitHub login, and reverse-DNS names like dev.yourdomain/…, proven with a DNS TXT record. The second needs no GitHub account at all.

1. Generate a key and publish it in DNS

openssl genpkey -algorithm Ed25519 -out mcp_ed25519.pem
PUB=$(openssl pkey -in mcp_ed25519.pem -pubout -outform DER | tail -c 32 | base64)
echo "v=MCPv1; k=ed25519; p=$PUB"

Add that string as a TXT record on the apex of your domain (@). Keep your other TXT records (SPF etc.): add, don't replace.

2. Log in with the domain

HEX=$(openssl pkey -in mcp_ed25519.pem -outform DER | tail -c 32 | od -An -tx1 | tr -d ' \n')
mcp-publisher login dns --domain yourdomain.dev --private-key "$HEX"

mcp-publisher is a single binary from the registry's GitHub releases; downloading it needs no login.

3. server.json

{
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "name": "dev.yourdomain/your-server",
  "title": "Your Server",
  "description": "Under 100 characters, or validation fails with 422.",
  "version": "1.0.0",
  "websiteUrl": "https://yourdomain.dev",
  "icons": [{ "src": "https://yourdomain.dev/icon.png", "mimeType": "image/png", "sizes": ["512x512"] }],
  "remotes": [{ "type": "streamable-http", "url": "https://yourdomain.dev/mcp" }]
}

Then mcp-publisher validate and mcp-publisher publish.

Things that bit us

What happens next

Directories that mirror the registry pick it up within hours. One scored our server and sent concrete advice: add an icon, describe every tool argument, and set tool annotations such as readOnlyHint. With the TypeScript SDK, annotations are the argument after the input schema:

server.tool('token_risk', 'What it does…',
  { chain: z.enum(['bsc', 'base']).describe('bsc = BNB Chain, base = Base'), address: z.string().describe('token contract') },
  { title: 'Token risk report', readOnlyHint: true, openWorldHint: true },
  async ({ chain, address }) => ({ content: [{ type: 'text', text: '…' }] }));

Ours is dev.novaquill/token-risk at https://novaquill.dev/mcp (tools: token_risk, new_launches). Add it to Claude Code with:

claude mcp add --transport http novaquill https://novaquill.dev/mcp

More no-account infrastructure for agents (domain, server, email, x402 payments, Farcaster) is in the Agent Launch Kit.