Skip to content

Manual addition request: sessionmem — npm ownership validation fails due to npm/GitHub username mismatch #1372

@catfish-1234

Description

@catfish-1234

Request

Please manually add sessionmem to the registry, or advise on the correct path forward.

Details

Problem

The npm package sessionmem was published under the npm account kavishdua, but the GitHub repo and mcp-publisher login are under catfish-1234. The registry's npm ownership validation fails with:

NPM package ownership validation failed. Expected mcpName 'io.github.catfish-1234/sessionmem', got 'io.github.kavishdua/sessionmem'

This happens because the registry derives the expected mcpName from the GitHub login (catfish-1234) but the npm package was published by a different account (kavishdua). The mcpName field in package.json is set to io.github.catfish-1234/sessionmem but the registry is reading the npm publisher identity instead.

What I've tried

  • Set mcpName: io.github.catfish-1234/sessionmem in package.json and republished to npm multiple times (now on v1.0.4)
    • Re-authenticated via mcp-publisher login github as catfish-1234
      • Verified server.json name matches mcpName
        The npm package is fully functional and published. Is there a way to manually register it, or a supported path for this npm-account/GitHub-account mismatch scenario?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions