400 error when trying to publish

[simasch]

I've successfully logged in using my domain.

But when trying to publish, I get

Error: publish failed: server returned status 400: {"title":"Bad Request","status":400,"detail":"Failed to publish server","errors":[{"message":"failed to check remote URL conflict: failed to query servers: failed to deallocate cached statement(s): conn busy"}]}

This is my server.json

{

  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-07-09/server.schema.json",
  "name": "ch.martinelli/jooq-mcp",
  "description": "An MCP server that provides access to the jOOQ documentation",
  "status": "active",
  "repository": {
    "url": "https://github.com/martinellich/jooq-mcp",
    "source": "github"
  },
  "version": "1.0.0",
  "remotes": [
    {
      "type": "sse",
      "url": "https://jooq-mcp.martinelli.ch/sse"
    }
  ]
}

I don't understand the problem, and there is no information on what's wrong.

[rdimitrov]

Hey, @simasch, thanks for raising this! I'm working on a fix that should help resolve this 👍

[joelvarty]

I'm seeing a similar issue, although not sure if it's the same thing.

server.json

{
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-07-09/server.schema.json",
  "name": "io.github.agility/agility-mcp-server",
  "description": "An MCP server that provides access to Agility CMS.  See https://mcp.agilitycms.com for more details.",
  "status": "active",
  "repository": {
    "url": "https://github.com/agility/agility-mcp-server",
    "source": "github"
  },
  "version": "1.0.0",
  "remotes": [
    {
      "type": "streamable-http",
      "url": "https://mcp.agilitycms.com/api/mcp"
    }
  ]
}

error message:

Error: publish failed: server returned status 400: {"title":"Bad Request","status":400,"detail":"Failed to publish server","errors":[{"message":"remote URL https://mcp.agilitycms.com/api/mcp does not match namespace io.github.agility/agility-mcp-server: remote URL host mcp.agilitycms.com does not match publisher domain agility.github.io"}]}

[domdomegg]

Sorry, this is an issue on our side with scaling up the registry to meet the demand - we're tracking it over in #400 and will be posting further status updates there :)

Apologies again, and thanks again for testing out registry in preview and bearing with us while we fix this. Excited to have these servers registered soon 🤞