Server published in Official Registry but not visible on github.com/mcp: io.github.mudrex/mcp-server

[DecentralizedJM]

Description

Our MCP server io.github.mudrex/mcp-server (Mudrex MCP Server) is successfully published and active in the Official MCP Registry, but does not appear in the GitHub MCP Registry at github.com/mcp.

Server Details

Server name: io.github.mudrex/mcp-server
Title: Mudrex MCP Server
Description: MCP server for Mudrex futures trading enabling AI agents to securely access data and risk tools.
Version: 1.0.0
Source repo: https://github.com/mudrex/mcp-server
Website: https://docs.trade.mudrex.com/docs/mcp
Transport: Streamable HTTP (https://mudrex.com/mcp)
Status: active since 2026-04-02

Evidence

Official Registry API returns it:

bash
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=mudrex"
Returns full server metadata with "status": "active" and "isLatest": true.

GitHub MCP Registry shows no results:

https://github.com/mcp?search=mudrex → No results

Request

Could the Mudrex MCP Server be ingested/synced to appear in the GitHub MCP Registry (github.com/mcp) alongside the 94+ servers currently listed there?

If automatic sync from the Official Registry is not yet available, can it be manually added?

Related

Discussion #506 — MCP server not showing up in github.com/mcp
Issue #1107 — Same problem reported by another publisher

[unitedideas]

There is a known ingestion lag between the Official Registry and github.com/mcp (discussion #506 tracks it, and issue #1107 reports the same symptom for another publisher). No manual override as far as I can tell — the UI pulls on its own schedule.

A couple of unblock-while-you-wait tips:

1. Verify the endpoint itself responds to an unauthenticated JSON-RPC probe. Several "visible in API, invisible in search" cases I have seen were actually endpoints that returned 401/404 to a minimal initialize-less call, which caused downstream indexers to drop the entry. You can self-check with Not Human Search’s verify_mcp tool:

   curl -s -X POST https://nothumansearch.ai/mcp \
     -H "Content-Type: application/json" \
     -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"verify_mcp","arguments":{"url":"https://mudrex.com/mcp"}}}'
   

   If it comes back verified: false, fix that first — the GitHub UI almost certainly probes similarly.

2. In the meantime, get listed on discovery surfaces that pull directly from your endpoint instead of a cached index. I just submitted io.github.mudrex/mcp-server to nothumansearch.ai (it will show up on the next crawl in a few hours), which at least gives agents an alternate discovery path while the GitHub UI catches up.

Not a fix for the underlying sync, but should keep you reachable in the interim.