Common server.json validation errors for the MCP registry
11/19/2026 — 11/19, 02:19·1 sources (all)·1 reports (all)
Key takeaways
- A DEV Community post lists the most common validation failures when submitting server.json to the official MCP registry, including descripti…
Background & analysis
On November 19, 2026, the AI section of DEV Community published an article reviewing the most common validation failures that occur when submitting a server.json file to the official MCP registry. The piece notes that anyone who has published, or attempted to publish, an MCP server to the official registry will have encountered server.json along with the validation process that quietly rejects submissions. The schema itself is compact, yet a small number of recurring mistakes account for the majority of failures.
The article checks each point against the current registry schema, dated 2025-12-11, and lists the errors that most often trigger a rejection. The first is a description that exceeds the 100-character cap; writing a promotional paragraph is described as the single most common reason a submission is turned down, and the article recommends replacing it with one concise sentence. The remaining mistakes are a missing top-level version field, packages entries that omit transport information, and version values written as latest or expressed as a range.
The available material does not mention any official response or follow-up changes from the registry side regarding these validation issues, so the matter currently rests at the stage of the article's summary of recurring validation errors and practical guidance for submitters.
AI-generated from 1 reports · updated 3 days ago
- Heat index
- 25
- All sources
- 1
- All reports
- 1
- First seen
- 3 days ago
Reports on this story headlines open the original
A DEV Community post lists the most common server.json validation failures when publishing an MCP server to the official registry, including descriptions over 100 characters, a missing root-level version, packages without a transport, and versions set to latest or a range. It checks against the current registry schema.
DEV Community · AIAI score 61
Other stories people are talking about
- Heat index 1143RisingAnthropic Reaches $1.6 Trillion Market Value in First Trading Week After IPO21 sources
- Heat index 1011Anthropic Mathematician Says Claude Formalized the Generalized Riemann Hypothesis21 sources
- Heat index 622Anthropic IPO total raise reaches $93.5 billion after greenshoe exercise20 sources
- Heat index 596RisingThinking Machines Lab Open-Sources Inkling 2 Mini with 32GB Model Card Recommendation10 sources
- Heat index 490RisingSEC probes Nvidia accounting practices as shares post seven-week slide9 sources
How is heat calculated?About the methodHide
Heat counts how many independent sources covered a story in the last 48 hours: one source counts once no matter how many posts it published, decaying with a 24-hour half-life. What ranks first is what many people are talking about.
This page aggregates public feeds. Headlines and summaries are machine-organized and remain the property of the original authors; verify important facts at the source. If you believe a headline or summary infringes your rights, email the contact address in the footer with the page URL and basis of your claim, and we will remove or replace it after review.
- Surge
- Discussion rising fast
- New
- First report within 6 hours
- Rising
- Still gathering discussion

