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?
Request
Please manually add
sessionmemto the registry, or advise on the correct path forward.Details
kavishdua)catfish-1234)io.github.catfish-1234/sessionmemio.github.catfish-1234/sessionmemProblem
The npm package
sessionmemwas published under the npm accountkavishdua, but the GitHub repo and mcp-publisher login are undercatfish-1234. The registry's npm ownership validation fails with: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). ThemcpNamefield inpackage.jsonis set toio.github.catfish-1234/sessionmembut the registry is reading the npm publisher identity instead.What I've tried
mcpName: io.github.catfish-1234/sessionmeminpackage.jsonand republished to npm multiple times (now on v1.0.4)mcp-publisher login githubascatfish-1234server.jsonname matches mcpNameThe 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?