R/RegistryReady

MCP REGISTRY · SERVER.JSON

Publish metadata
that passes first time.

Validate an MCP Registry server.json against practical requirements from the official 2025-12-11 schema. Everything stays in your browser.

INPUT

server.json

0 B / 4 KB
REPORT

Publish readiness

—
Waiting for metadata

Paste a server.json document or load the official-style example.

QUICK START

Generate a minimal server.json

Fill in the essentials. The generated document uses the current official schema URL and can be validated immediately.

CHECK COVERAGE

More than JSON syntax.

01

Registry identity

Checks reverse-DNS-style names, descriptions, versions, repository URLs, and the current schema reference.

02

Distribution

Reviews packages and remotes, supported registries, identifier/version parity, HTTPS endpoints, and transports.

03

Publish safety

Flags embedded credential values, oversized files, placeholders, hard-coded local endpoints, and common field-name mistakes.

BEFORE MCP-PUBLISHER

A practical preflight

  1. 1Match namesYour published package should declare the same mcpName as server.json.
  2. 2Match versionsThe server and package version should identify the same immutable release.
  3. 3Keep secrets declarativeDescribe secret inputs with variables; never paste a real token into registry metadata.
  4. 4Test, then publishRun the official publisher validation after this browser preflight.
MCP server.json generatorBuild metadata field by field →MCP Registry publish checklistAvoid common rejection causes →Remote MCP server.jsonModel HTTPS endpoints and headers →

PURPOSE & METHODOLOGY

A focused tool, with the context to use it well

RegistryReady was created to validate and generate server.json metadata for the official MCP Registry workflow. It is intended for MCP server maintainers preparing registry submissions. The tool is free, requires no account, and is paired with original explanations so you can understand the result rather than copy an unexplained output.

How to use the result

Start with a sample or a non-sensitive copy of your data, run the check, and review every finding before changing a production project. Validation covers structure, package metadata, remotes, and publication readiness. Checklists explain the surrounding release process so the site offers more than schema validation alone. Specifications and software evolve, so confirm high-impact decisions against the linked primary documentation.

Privacy and limitations

MCP server.json metadata is processed in your browser wherever the tool page states that local processing is used. Avoid entering passwords, access tokens, personal data, or confidential material. Automated output may be incomplete because it cannot know your entire deployment, threat model, or organizational policy.

Independent and transparent

This is an independent developer resource, not an official certification service. Source code and issue tracking are available on GitHub. Read more about the project, review the privacy policy, or report an error.