Skip to content

Published server not appearing in search results (io.github.ARCXS-Protocol/mcp-server) #1173

@GitIdol

Description

@GitIdol

Summary

We successfully published a server to the registry on April 12, 2026 using mcp-publisher v1.5.0. The publish command returned ✓ Successfully published and attempting to re-publish returns "cannot publish duplicate version" — confirming the server exists in the registry database. However, the server does not appear in any search results via the API.

Server Details

  • Name: io.github.ARCXS-Protocol/mcp-server
  • Version: 1.0.2
  • npm package: @arcxs-protocol/mcp-server (published, includes mcpName field)
  • Auth method: GitHub OAuth (org membership public)
  • Published: April 12, 2026

Steps to Reproduce

  1. Published via mcp-publisher publish — received success confirmation
  2. Attempted GET /v0.1/servers?q=arcxs — not found (30 results returned, none matching)
  3. Attempted GET /v0.1/servers?q=ARCXS-Protocol — not found
  4. Attempted GET /v0.1/servers?q=universal+agent+registry — not found
  5. Attempted re-publish — rejected with "cannot publish duplicate version" (confirming it exists)

Expected Behavior

The published server should appear in search results when querying by name or description keywords.

Questions

  1. Is there a review/approval step after publishing that we may be waiting on?
  2. Does the search API have pagination beyond the initial 30 results? All results we see start with "a" alphabetically.
  3. Is there a way to check the status of a published server (active, pending, etc.)?

Environment

  • mcp-publisher v1.5.0 (Homebrew)
  • Registry API: https://registry.modelcontextprotocol.io
  • Auth: GitHub OAuth, io.github.ARCXS-Protocol/* namespace

Thanks for building this registry — excited to be part of the ecosystem.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions