What
Please remove the registry entry io.github.jarvis-intelligence/jarvis (versions 0.6.1, 0.6.2, 0.7.2, 0.8.0).
Why
The backing GitHub repository jarvis-intelligence/jarvis was transferred back to its original owner at phuongddx/jarvis (old URL 301-redirects). The registry namespace follows the publishing identity, so from v0.8.1 the package publishes as io.github.phuongddx/jarvis (already live: version 0.8.1, PyPI package jarvis-mcp). The jarvis-intelligence entry is a frozen stale duplicate of the same package pointing at the same PyPI distribution.
History: the project published as io.github.phuongddx/jarvis through 0.6.0, moved to the org (splitting the namespace) for 0.6.1–0.8.0, and has now moved back.
Authorization
I'm the owner of both the GitHub repo (phuongddx, admin of jarvis-intelligence) and the PyPI project jarvis-mcp that both entries point at. Happy to re-verify via mcp-publisher login github if a maintainer prefers that route over direct removal.
Thank you!
What
Please remove the registry entry
io.github.jarvis-intelligence/jarvis(versions 0.6.1, 0.6.2, 0.7.2, 0.8.0).Why
The backing GitHub repository
jarvis-intelligence/jarviswas transferred back to its original owner atphuongddx/jarvis(old URL 301-redirects). The registry namespace follows the publishing identity, so from v0.8.1 the package publishes asio.github.phuongddx/jarvis(already live: version 0.8.1, PyPI packagejarvis-mcp). Thejarvis-intelligenceentry is a frozen stale duplicate of the same package pointing at the same PyPI distribution.History: the project published as
io.github.phuongddx/jarvisthrough 0.6.0, moved to the org (splitting the namespace) for 0.6.1–0.8.0, and has now moved back.Authorization
I'm the owner of both the GitHub repo (
phuongddx, admin ofjarvis-intelligence) and the PyPI projectjarvis-mcpthat both entries point at. Happy to re-verify viamcp-publisher login githubif a maintainer prefers that route over direct removal.Thank you!