Impersonation: io.github.jimmybr-PDX/rugradar copies an existing product's name and description (RugRadar)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 8/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 领域
- backend
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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/rugradarv1.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:
io.github.jimmybr-PDX/rugradar, published 14 Oct 2026 05:00 UTC, status active- Title: "RugRadar"
- Description: "Rug-pull, token-safety and honeypot risk checks for Solana and EVM tokens. $0.01 per call."
- Website: https://x402-seller-pmlm.onrender.com/rugradar
- Repository: https://github.com/jimmybr-PDX/x402-seller
- Remote: https://x402-seller-pmlm.onrender.com/mcp (header
X-RugRadar-Key, prepaid credit)
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.
- 主要语言
- Go
- 星标
- 7.3k
- 派生
- 1k
- 平均合并
- 3 天 14 小时
- 30 天内合并 PR
- 12
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
modelcontextprotocol/registry 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 65/100
modelcontextprotocol/registry#1713 ·
维护者通常 1 天内回复
-
3 registry records that cannot resolve for any client, and a caution about single-pass dead counts未关闭
难度 2/5 1-3 小时 新手友好度 68/100
modelcontextprotocol/registry#1692 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 80/100
modelcontextprotocol/registry#1657 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 68/100
modelcontextprotocol/registry#1652 ·
维护者通常 1 天内回复
-
IsValidRemoteURL only blocks literal localhost/127.0.0.1 — misses [::1], 127.0.0.0/8, 0.0.0.0, and private/link-local addresses可能已有人在做 @amitvijapur 于 88 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 74/100
modelcontextprotocol/registry#1465 · 1 条评论 ·
维护者通常 1 天内回复
查看 modelcontextprotocol/registry 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
BurntSushi/toml#530 ·
-
难度 2/5 1-3 小时 新手友好度 77/100
维护者通常 1 天内回复
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:session-state issue-rating: 🦞 diamond lobster no-stale P2
难度 2/5 1-3 小时 新手友好度 74/100
openclaw/wacli#503 · 1 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
[Bug] rmqctl error diagnostics emit terminal control characters可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 81/100
apache/rocketmq-dashboard#6895 ·
维护者通常 3 天内回复