Request: rename or delete listing `dev.stackbilt.mcp/gateway` (confusing .dev TLD reversal)

[stackbilt-admin]

We published our MCP server to the registry on June 18 using the standard
reverse-DNS name format, but our domain (mcp.stackbilt.dev) produces
dev.stackbilt.mcp/gateway — which reads as a development or staging
namespace rather than a production server.

Current listing: dev.stackbilt.mcp/gateway (v1.1.0)
Repository: https://github.com/Stackbilt-dev/stackbilt-mcp-gateway
Remote: https://mcp.stackbilt.dev/mcp (streamable-http)

We'd like to re-publish as stackbilder/mcp-gateway to match our product
name and avoid the staging-namespace confusion. Since the name field is
immutable once published, we're requesting either:

1. Deletion of the current dev.stackbilt.mcp/gateway entry so we can
   re-publish with the correct name, or
2. Rename to stackbilder/mcp-gateway if that's supported on your end.

Happy to verify ownership however needed. Thanks for the consideration —
the registry is in preview so flagging this early seems useful for the
name format guidance as well (.dev TLD owners will all hit this).

[pree-dew]

@stackbilt-admin Thank you for reaching out, in order to mark your server as deleted you can follow the documentation:

API: https://registry.modelcontextprotocol.io/docs#/operations/update-server-status-v0.1
CLI: https://github.com/modelcontextprotocol/registry/blob/main/docs/reference/cli/commands.md#mcp-publisher-status