MCP-DSC-004
Extension identifiers use a valid non-reserved reverse-DNS prefix
“Extension identifiers MUST follow the _meta key naming rules, with a mandatory prefix.” — spec anchor
How to fix this
Prefix every extension identifier in `_meta` with a reverse-DNS domain you control, such as `com.example/myFeature`. The `io.modelcontextprotocol/` prefix is reserved for fields the specification defines.
Check your own server against this rule
The validator makes real protocol requests and reports this rule as pass, warn or fail alongside the other 78. Validate a server or read how the check works.
Other Discovery and capabilities rules
- MCP-DSC-001server/discover is implemented
- MCP-DSC-002DiscoverResult advertises supported protocol versions
- MCP-DSC-003Advertised versions include a currently-supported revision
- MCP-DSC-005Results carry io.modelcontextprotocol/serverInfo in _meta