Request: mark legacy io.github.402signal/402signal as superseded by io.github.402signalhq/402signal

402Signal now publishes under the canonical io.github.402signalhq/402signal namespace, but the older io.github.402signal/402signal entry remains active and isLatest=true with an obsolete $0.01 description. Downstream registries such as mcpi.app display both identities, preserving incorrect pricing.

Observed from https://registry.modelcontextprotocol.io/v0.1/servers?search=402signal:

• Legacy: io.github.402signal/402signal v0.3.0, active, published 2026-08-30, remote https://402signal.com/mcp, obsolete $0.01 text.
• Canonical: io.github.402signalhq/402signal v0.3.1, active, published 2026-09-04, remote https://402signal.com/mcp/v0.3.1, correct $0.003 success-only text.

Please mark the legacy identity as deprecated/superseded, or advise the supported migration process so downstream consumers prefer the canonical identity. This request is to correct discovery, not to disable https://402signal.com/mcp, which remains supported. Published version metadata is immutable according to the FAQ; no attempt has been made to overwrite v0.3.0.

Canonical public source: https://github.com/402signalhq/402signal. The former https://github.com/402signal/402signal URL redirects there. Current deployed pricing and identity are documented at https://402signal.com/rails and https://402signal.com/llms.txt.

I can provide domain ownership verification if needed. Contact: ross@402signal.com.

Start with the registry API search result for 402Signal and trace how server identities, active/latest status, and supersession or deprecation are represented. Check the registry FAQ and repository guidance for the supported migration process, since published version metadata is immutable. Done means downstream discovery prefers io.github.402signalhq/402signal without disabling the supported endpoint.