modelcontextprotocol / modelcontextprotocol/registry

Request: deprecate retired io.github.janus-ubos-republic/janus-kinematic-drive entries

Open
#1,535 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

Server

io.github.janus-ubos-republic/janus-kinematic-drive

The official API currently returns versions 0.1.1 and 0.1.3 as active. Both describe the retired Janus concierge and pin yanked PyPI releases.

Requested action

Please set all versions to deprecated (or deleted if that is the preferred retirement policy) with this status message:

Retired standalone product; superseded by UBOS Sovereign Desk. No payment is accepted. See https://github.com/janus-ubos-republic/janus-kinematic-drive for the retirement notice.

Ownership and evidence
  • The source repository is now archived by its owner and visibly marked retired:
    https://github.com/janus-ubos-republic/janus-kinematic-drive
  • PyPI ubos-janus-mcp versions 0.1.0 through 0.1.3 are yanked; 0.1.4 is an inactive, fail-closed retirement notice.
  • The old HTTP routes return permanent 410 Gone retirement JSON and never issue payment instructions.
  • I am opening this as ubos-republic, an administrator of the source repository. GitHub OAuth through mcp-publisher authenticated successfully but the status update returned 403, so I cannot complete the documented PATCH directly.

This is a truthfulness/deprecation request, not a security incident. 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 with the official API entries for io.github.janus-ubos-republic/janus-kinematic-drive and the documented PATCH operation. Verify versions 0.1.1 and 0.1.3, then apply the requested retirement status and message, or the registry's preferred deleted status. Done means both versions no longer appear active and the API reports the retirement information.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
api, backend
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.