Onboarding request: io.github.LambdaTest/mcp for github.com/mcp

[keys-github]

Our server is published and active on the official MCP registry but does not appear on github.com/mcp.
▎
▎ | | |
▎ |-------------|--------------------------------------------------|
▎ | Server name | io.github.LambdaTest/mcp |
▎ | Version | 1.0.1 (isLatest: true, status: active) |
▎ | Published | 2026-08-03T14:45:31Z |
▎ | Repository | https://github.com/LambdaTest/mcp-server-guide |
▎ | Endpoint | https://mcp.lambdatest.com/mcp (streamable-http) |
▎
▎ curl -s "https://registry.modelcontextprotocol.io/v0/servers?search=LambdaTest"
▎
▎ https://github.com/mcp?search=LambdaTest returns no results. The catalog grew from 191 to 210 entries between Aug 3 and Aug 7, including several remote-only servers with a docs repository and no license or
▎ topics — the same profile as ours — so we don't believe we're missing a prerequisite. Is anything else needed from our side?

Can anyone help in this?

[stefisha]

This looks more like a GitHub catalog ingestion/curation issue than a publishing problem.

The official MCP Registry is a source of metadata, but downstream catalogs such as github.com/mcp can import it asynchronously and apply their own filtering or curation. Being active in the official registry therefore may not result in immediate catalog inclusion.

Since io.github.LambdaTest/mcp is returned as active and latest by the Registry API, I don’t think another publication step is required from your side. I would verify that the latest-version endpoint, repository metadata and remote MCP endpoint remain accessible, then wait for the GitHub team to confirm the catalog’s sync schedule or any undocumented inclusion criteria.

The details you provided should be enough for them to trace the import. 😊