Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Impersonation: io.github.jimmybr-PDX/rugradar copies an existing product's name and description (RugRadar)

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

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
8/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Domain
backend

Research direction

This is a moderation and impersonation dispute about a published listing, not a code change, and the payload names no files, tests or entry points. A newcomer cannot finish it by editing the repository. It needs a registry maintainer to review the listing and decide on removal under the project's dispute process. Done means a maintainer has ruled on the report, not that a patch has merged.

Written by the indexing model from the issue text.

Description

Impersonation report

Hi team, I need to report a listing that appears to impersonate an existing product published in this registry.

Our product (prior use):

  • RugRadar, a free token-safety / honeypot checker, live at https://rugradar-dun.vercel.app
  • Publicly launched 12 Oct 2026 (launch post: https://x.com/The_Real_EJC/status/2109675509726450112)
  • Registered in this registry since 6 Oct 2026 as io.github.Darkjay123/rugradar v1.0.0 (we marked that version deleted today while consolidating into an ownership-verified domain namespace; publish timestamp visible in registry history)
  • Canonical entry now: app.vercel.rugradar-dun/rugradar-mcp (status: active, ownership verified via the HTTP challenge on rugradar-dun.vercel.app)

The listing at issue:

Why we believe this is impersonation: the name ("RugRadar"), title, and product description ("rug-pull, token-safety and honeypot risk checks") closely mirror our product and wording, and the listing was published after both our 6 Oct registry registration and our 12 Oct public launch, pointing at an unrelated endpoint and repository, and monetizing per call. To anyone (or any agent) browsing the registry, this entry reads as our product. It is not.

Request: could the maintainers review io.github.jimmybr-PDX/rugradar for impersonation and remove it, or advise the correct process for this kind of dispute? Happy to provide any additional evidence (launch archives, registry history timestamps).

Thanks.

Dominant language
Go
Stars
7.3k
Forks
1k
Avg merge
3d 21h
Merged PRs (30d)
14

Getting set up

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.

More from modelcontextprotocol/registry

All issues in modelcontextprotocol/registry

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.