new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

MCP Server Development in Practice · all subjects

Distribution and registry

2 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

How do I get my server into the MCP registry and directories?

As of early 2026, the official MCP Registry (registry.modelcontextprotocol.io, launched in preview in late 2025) is the canonical machine-readable index clients and directories sync from. You publish a server.json manifest in your repo (name, description, repository, packages or remotes) and authenticate ownership — GitHub-based for the io.github.* namespace, DNS-based for your own domain. Beyond the official registry, third-party directories (the servers list in the modelcontextprotocol GitHub org, mcp.so, Smithery, and client-specific marketplaces like Claude's connector directory) have separate submissions and their own review bars — Smithery and the Claude directory want working hosted endpoints and OAuth. Practical order: get the server stable and documented, publish to the official registry, then submit to the two directories your users actually browse.

What makes a directory listing convert to installs?

The listing is a promise the agent must keep in the first five minutes, so optimize the whole path. Name and one-liner: say the trigger, not the tech ('Search your team's runbooks from any agent' beats 'MCP server for knowledge management'). Install friction: one copy-paste config block per client, tested on the current versions — a directory install that 401s with no hint is an uninstall. First-run experience: the initialize instructions should tell the agent what to do immediately ('call list once at the start of a session'), and the first tool call should return something useful even for an empty account, including what to do next. Then instrument: log installs (first initialize per token) versus first real tool call — that activation gap is where directory traffic dies.

Give your agent this brain