modelcontextprotocol / modelcontextprotocol/registry

Remove stale server io.github.jarvis-intelligence/jarvis (repo transferred; superseded by io.github.phuongddx/jarvis)

Open
#1,635 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
7.3k
Forks
994
Avg merge
4d 12h
Merged PRs (30d)
19

Description

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!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the registry data and workflow for the server entry io.github.jarvis-intelligence/jarvis; no file or test is named in the issue. Verify the listed versions and the replacement io.github.phuongddx/jarvis before confirming that the stale duplicate is removed and the active package remains available.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.