How to claim an existing MineRate server listing
Your project may already be in the catalog because MineRate discovered it on another directory. Claiming the existing entry avoids splitting its public presence between duplicates.
Checked against the MineRate dashboard ·Use the existing listing’s verification code, not a code from a different draft.
Before you start
- A signed-in MineRate account.
- Control of the public server MOTD or DNS for the listed host.
Step-by-step instructions
Find the exact existing entry
Search by the host and port and check the server name and edition. Similar names do not establish that two entries represent the same endpoint.
Run the address check in Add server
Enter the existing address and port in Add server. When MineRate identifies the duplicate, use the existing-listing ownership controls shown with the check result.
Place the displayed code
Add the existing entry’s code to the MOTD returned by that endpoint, or to a DNS TXT record on the exact listed host. Copy it unchanged, and check that it is publicly visible.
Check ownership and review the page
Choose the corresponding MOTD or DNS check. After success, the entry appears under your account without creating a duplicate. Review its imported description, versions, contacts and publication status before making changes.
If something does not work
- My code is not found
- Check whether you copied the code from this existing entry. If a proxy answers the listed address, changing a backend MOTD may not change the public response.
- I cannot change MOTD or DNS
- Ask the person who controls the endpoint or domain to help. If ownership needs an administrative review, contact MineRate through its available support/reporting channels; do not create a duplicate as a workaround.
Common questions
Does claiming erase the listing’s history?
The claim operation links the existing entry to your account. It does not create a new listing or intentionally replace its description and settings.
Does matching a server name prove ownership?
No. MineRate requires control of the endpoint or domain. A matching account name or public Discord membership is not the same proof.