Remove stale duplicate entries io.github.edgarfloresguerra2011-a11y/marketnow* (superseded by DNS-verified site.marketnow/marketnow)
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 80/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- tooling
Research direction
The issue is about removing three stale entries from a registry. The entries are clearly named: io.github.edgarfloresguerra2011-a11y/marketnow (v1.4.1, v1.5.0) and io.github.edgarfloresguerra2011-a11y/marketnow-mcp (v1.0.0). Find the registry data file (likely JSON or YAML) that lists these entries and delete them. Verify the correct, active entry is site.marketnow/marketnow. Ensure the file format remains valid after removal.
Written by the indexing model from the issue text.
Description
These three entries were published from a GitHub account the project owner can no longer access. They advertise outdated skill counts (8,764 / 8,845 / 13,800+) and point to a repository that returns 404:
io.github.edgarfloresguerra2011-a11y/marketnow(v1.4.1, active)io.github.edgarfloresguerra2011-a11y/marketnow(v1.5.0, active, isLatest)io.github.edgarfloresguerra2011-a11y/marketnow-mcp(v1.0.0, deprecated)
The same project is now published under a DNS-verified identity: site.marketnow/marketnow (v1.14.2, active, isLatest), verified via the TXT record at the marketnow.site apex (v=MCPv1; k=ed25519) and maintained by the domain owner. The stale entries misrepresent the project's current state in downstream directories (TensorBlock, PulseMCP) that ingest this registry.
Requesting removal or deprecation of the three stale entries. Happy to provide any additional proof of domain/project ownership.
- Dominant language
- Go
- Stars
- 7.3k
- Forks
- 1k
- Avg merge
- 3d 21h
- Merged PRs (30d)
- 14
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from modelcontextprotocol/registry
-
3 registry records that cannot resolve for any client, and a caution about single-pass dead countsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
modelcontextprotocol/registry#1692 ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
modelcontextprotocol/registry#1652 ·
Maintainers usually reply within 2 days
-
IsValidRemoteURL only blocks literal localhost/127.0.0.1 — misses [::1], 127.0.0.0/8, 0.0.0.0, and private/link-local addressesPossibly taken @amitvijapur claimed this 85 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
modelcontextprotocol/registry#1465 · 1 comment ·
Maintainers usually reply within 2 days
-
GitLab repository URLs with nested groups/subgroups are rejected by validatorPossibly taken @anneheartrecord claimed this 124 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 84/100
modelcontextprotocol/registry#1359 ·
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 8/100
modelcontextprotocol/registry#1708 ·
Maintainers usually reply within 2 days
All issues in modelcontextprotocol/registry
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
SAP/crossplane-provider-btp#1118 ·
Maintainers usually reply within 1 day
-
benchmark: `make setup` fails because audit-exporter builds with Go 1.25.0 while go.mod requires 1.26.0Possibly taken @xsvm claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 84/100
volcano-sh/volcano#6097 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
[Bug]: Bedrock invoke-with-response-stream reports `stop_reason: "end_turn"` for tool-use turnsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day