MCP Registry Manifest creates and validates deterministic server.json metadata for the official MCP Registry. Every result identifies the dated schema source, the date it was checked, and the exact schema digest used, so generated files and validation evidence can be reproduced later.
Generation follows stable field ordering and immediately validates the result. Validation uses a complete embedded snapshot of the checked official schema rather than silently switching to a moving draft.
What you can do
- generate_manifest — build a minimal remote-server manifest with stable JSON formatting
- validate_manifest — validate any server.json object and receive sorted schema errors
- Record the checked schema version, source URL, date, and SHA-256 digest
- Prepare remote Streamable HTTP or legacy SSE registry metadata
Who it's for
MCP server publishers, release engineers, registry maintainers, and documentation teams. It is useful when registry metadata must stay reviewable and reproducible across releases.
How to use it
- Start with generate_manifest and provide the registry name, description, version, and public remote URL
- Add repository and website fields when they are verified
- Review validation before saving or publishing the generated JSON
- Use validate_manifest on hand-edited files or CI inputs
Getting started
Generate a minimal remote manifest, then keep the returned schema provenance alongside any publication evidence.
