Request inclusion of megalinter-mcp in the GitHub MCP registry

[carldawson-bca]

Hi GitHub team, I would like to request inclusion of io.github.DownAtTheBottomOfTheMoleHole/megalinter in the curated GitHub MCP registry. It is published in the official MCP registry (https://registry.modelcontextprotocol.io/servers/io.github.DownAtTheBottomOfTheMoleHole/megalinter) at version 3.0.0, but does not appear in https://api.mcp.github.com/v0/servers results. Could you advise inclusion criteria and add it if eligible? Thanks.

[GloriousMir]

Thanks for raising this. The GitHub MCP registry exposed through https://api.mcp.github.com/v0/servers is a curated subset of servers from the official Model Context Protocol registry, so not every server published at registry.modelcontextprotocol.io automatically appears there. Inclusion typically depends on factors such as stability, security review, maintenance status, and overall usefulness to the GitHub ecosystem.

Since io.github.DownAtTheBottomOfTheMoleHole/megalinter is already published in the official MCP registry, the next step is usually to submit a request or proposal for inclusion in the curated GitHub MCP registry, which is essentially what you’ve done here. The GitHub team generally reviews these requests and decides whether the server meets their curation criteria.

In the meantime, developers can still use the MCP server directly from the official MCP registry, even if it’s not listed in the GitHub-curated endpoint yet. If possible, it may help to provide additional details such as:

• the GitHub repository of the MCP server
• documentation on security and maintenance
• example use cases with Copilot or MCP clients

This can make it easier for the maintainers to evaluate and potentially include it in the GitHub MCP registry.

[SIMARSINGHRAYAT]

Great request! Building on what GloriousMir mentioned, here's what typically helps with MCP registry inclusion:

Current Status:
Your megalinter-mcp is in the official registry but not yet in GitHub's curated subset. This is normal - many quality tools follow this path.

Next Steps for Curation Approval:

1. Ensure Documentation is Excellent:

   • Clear README with usage examples
   • Installation instructions for various platforms
   • Detailed feature documentation
   • Troubleshooting guide

2. GitHub Profile Quality:

   • Recent commit activity
   • Active maintenance and issue responses
   • Clear issue/PR management
   • Semantic versioning
   • Changelog updates

3. Community Engagement:

   • Respond actively to issues
   • Maintain code quality
   • Consider security reviews
   • Share benchmarks/performance data

4. Formal Submission:

   • The GitHub team reviews curation requests periodically
   • You may need to explicitly request curation (check GitHub MCP docs for process)
   • Evidence of real-world usage helps

What Helps Selection:

• Stability & reliability track record
• Security and maintenance commitment
• Integration quality (how well it works with Copilot/other tools)
• Community adoption metrics
• Clear value proposition for developers

In the Meantime:

• Tools available in official registry are fully functional
• Share your tool with relevant communities
• Consider posting about megalinter-mcp on GitHub Discussions/Copilot channels
• Gather feedback and testimonials from users

Timeline Expectations:

The GitHub team generally reviews curation candidates quarterly. Having strong evidence of quality and utility speeds up the process significantly.

Good luck with megalinter-mcp! The fact it's already in the official registry shows it's already valuable to the community.

[Sandeshkadel]

1. Understanding the Context

You want to include megalinter-mcp in the GitHub MCP (Model Context Protocol) registry. Here are the key points:

Repository / MCP server: io.github.DownAtTheBottomOfTheMoleHole/megalinter

Official MCP registry link: MCP Registry link

Version: 3.0.0

Problem: It does not appear in the GitHub MCP API (https://api.mcp.github.com/v0/servers) results.

This means the GitHub MCP registry has not synced this server yet.

2. How MCP Registry Inclusion Works

The GitHub MCP registry has a curated list of MCP servers that are eligible for display via the API. Typically, inclusion criteria include:

Official MCP-compliant server

The MCP server must implement the protocol correctly (exposes /manifest, /models, etc.) and be reachable.

Versioning

The server must have a valid semantic version. You already have version 3.0.0, which is compliant.

Public accessibility

The server must be publicly reachable over HTTPS without authentication (or with supported auth mechanisms).

Registration with the GitHub MCP registry

Simply being in the “official MCP registry” does not automatically push it to GitHub’s curated MCP API. GitHub has a curation step where servers are validated and added.

3. Why megalinter is not showing

From the information provided:

It exists on the official MCP registry: ✅

But it’s missing from the GitHub MCP API: ❌

Possible reasons:

Not yet requested for GitHub MCP

GitHub requires an explicit request to include a server in their curated API.

Validation failed

If the GitHub MCP maintainers tested it and something did not comply with their MCP rules (e.g., manifest missing fields, API unreachable, invalid metadata), it would not appear.

Propagation delay

Sometimes inclusion takes a few days after approval.

4. Recommended Steps to Resolve

Here’s a detailed workflow to get your MCP server included:

Step 1: Verify MCP Server Compliance

Make sure your MCP server exposes the required endpoints:

GET /manifest
GET /models
GET /versions

Validate JSON responses match MCP v1.0+ specs.

Make sure metadata like id, version, description, and authors is correct.

You can use the official MCP validator:

https://registry.modelcontextprotocol.io/validator
Step 2: Confirm Public Accessibility

Ensure https://registry.modelcontextprotocol.io/servers/io.github.DownAtTheBottomOfTheMoleHole/megalinter is accessible from the internet.

If it requires authentication, GitHub MCP cannot include it.

Step 3: Submit Inclusion Request to GitHub MCP

You already started this in GitHub Copilot Conversations. To make it actionable:

Open an issue in the GitHub MCP repo (if not already done).
Suggested template:

Title: Request inclusion of megalinter-mcp in GitHub MCP registry

Body:

Hello GitHub MCP team,

I would like to request inclusion of our MCP server:

• MCP server: io.github.DownAtTheBottomOfTheMoleHole/megalinter
• Official registry link: https://registry.modelcontextprotocol.io/servers/io.github.DownAtTheBottomOfTheMoleHole/megalinter
• Current version: 3.0.0

The server is fully MCP-compliant, publicly accessible, and validated. Could you advise the next steps or include it in the curated GitHub MCP registry?

Thank you.

Tag the request with relevant labels (mcp, registry, inclusion-request) if possible.

Step 4: Follow Up with GitHub MCP Maintainers

Maintainers typically respond after verifying compliance.

They may ask you to fix metadata, add additional fields, or provide documentation.

Once approved, your server will appear in:

https://api.mcp.github.com/v0/servers
Step 5: Monitor Inclusion

After approval, check API responses:

curl https://api.mcp.github.com/v0/servers | grep megalinter

Inclusion can take hours to a few days.

5. Optional: Self-Hosting MCP API Proxy

While waiting for GitHub approval, you could:

Maintain your own MCP API endpoint that mirrors megalinter.

This allows your clients to use MCP tooling immediately, even before GitHub’s curated API lists it.