Onboarding Request- Checkmarx MCP Server Published But Not Visible on github.com/mcp Registry

[cx-anand-nandeshwar]

Hi Team,

I hope you are doing well!

We have successfully published our Checkmarx MCP to public official MCP registry.
Refer the link: https://registry.modelcontextprotocol.io/?q=Checkmarx

We would like to request include our MCP into the GitHub MCP registry (https://github.com/mcp). Please find the request (150713).

The Checkmarx MCP endpoint is now tenant-specific and must be dynamically constructed using customer-provided values.
The following parameters are required during configuration:

CXONE_BASE_URL – Checkmarx tenant base URL
TENANT_ID – Checkmarx tenant identifier

We would like OAuth 2.0 to be presented as the default and recommended authentication method for customers configuring the Checkmarx MCP integration.

Our preferred MCP configuration is shown below:

{
  "mcpServers": {
    "Checkmarx": {
      "type": "http",
      "url": "https://${CXONE_BASE_URL}/api/security-mcp/mcp/${TENANT_ID}"
    }
  }
}

We would be happy to provide any additional technical details, participate in validation testing, or collaborate with your team to identify the most appropriate solution.
Thank you for your time and assistance. We look forward to your guidance.

@trent-j

Best Regards,
Anand Nandeshwar

[stefisha]

The tenant-specific URL may be the reason this entry needs additional handling.

For remote servers, the official MCP Registry supports URL template variables using {variable} syntax and a variables map. ${CXONE_BASE_URL} is shell-style interpolation and may not be understood by downstream catalogs.

I would publish the remote configuration in server.json like this:

{
  "remotes": [
    {
      "type": "streamable-http",
      "url": "{cxone_base_url}/api/security-mcp/mcp/{tenant_id}",
      "variables": {
        "cxone_base_url": {
          "description": "Checkmarx tenant base URL, including https://",
          "isRequired": true
        },
        "tenant_id": {
          "description": "Checkmarx tenant identifier",
          "isRequired": true
        }
      }
    }
  ]
}

OAuth discovery can then happen after the client resolves the customer-specific endpoint.

If the published Registry entry already uses this structure and is active, the remaining issue is likely GitHub’s asynchronous ingestion or its support for templated remote URLs. The GitHub team would need to confirm whether github.com/mcp currently supports these variables and its inclusion schedule.

Official remote-server publishing specification: https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/docs/registry/remote-servers.mdx