registry

Summary generates a template with (snake_case), but the registry API rejects it and expects (camelCase). The CLI does not convert between the two formats. Steps to reproduce 1. → generates template with , , , 2. Fill in the template 3. (in GitHub Actions with ) 4. Error Expected behavior Either: The CLI should convert snake_case fields to camelCase before sending to the API, or The init template should generate camelCase fields matching the API schema Additional context version: v1.0.0 Schema: Running in GitHub Actions with OIDC auth

I own both the GitHub org and the domain . I published (v1.0.0) with remote URL . I've since verified my domain via DNS and want to migrate to using the same remote URL, but publishing fails because v1.0.0 of the old entry still claims the URL: I published v3.0.0 of the old entry with a dummy remote URL (), but the registry still blocks because v1.0.0 retains the original URL and versions are immutable. Could an admin please either: 1. Delete entirely, or 2. Set all versions of to status This will free up the remote URL so I can publish under my verified domain namespace . Thank you!

Environment mcp-publisher v1.0.0 (Windows amd64) PowerShell 7.6.0 and Git Bash (MINGW64) server.json validated manually with correct camelCase fields Behavior mcp-publisher publish converts camelCase fields in packages[] to snake_case before sending to the API. The API validates against the camelCase schema and rejects the request with 422. Fields affected: registryType → sent as registry_type environmentVariables → sent as environment_variables isRequired → sent as is_required isSecret → sent as is_secret Steps to reproduce mcp-publisher init generates a template with snake_case fields Manually correct to camelCase per the schema at https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json mcp-publisher publish still sends snake_case server.json (verified with cat before publish) json{ "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json", "name": "io.github.GUARDIANCHAIN-GC-1/gc1", "description": "Non-custodial AI governance evidence. 6 blockchains. 38 tools.", "repository": { "url": "https://github.com/GUARDIANCHAIN-GC-1/GC-1", "source": "github" }, "version": "1.0.0", "packages": [ { "registryType": "npm", "identifier": "@guardianchain-llc/gc1", "version": "1.0.0", "transport": { "type": "stdio" } } ] } API error response json{ "title": "Unprocessable Entity", "status": 422, "detail": "validation failed", "errors": [ { "message": "expected required property registryType to be present", "location": "body.packages[0]" }, { "message": "unexpected property", "location": "body.packages[0].registry_type" } ] } Expected behavior mcp-publisher publish should send the JSON fields exactly as written in server.json without case conversion, or mcp-publisher init should generate the schema the API actually accepts.