VerifyMC.
Sign inGet started
GETTING STARTED

Your connection
starts here.

Set up your account, get your server role reviewed, and connect your existing VerifyMC service.

01. Apply for server access

Create an account and confirm your email. In your workspace, submit your Minecraft username, server address and port, role, and an HTTPS link to supporting evidence.

Each application includes a random ownership challenge. Add it to your server MOTD or provide other verifiable server-side evidence. Co-owners and administrators should also provide confirmation from the owner. The review is manual; a challenge alone does not grant access.

Decisions and requests for evidence appear in your application history. If more evidence is requested, use Respond with evidence on your application to update the link and resubmit it for review.

02. Create and configure a bridge

Once approved, create a bridge in your workspace. Save the credential immediately: it is shown once and cannot be retrieved later. You can rotate it if it is lost.

  1. Keep your existing Node.js VerifyMC service and SMTP configuration.
  2. Set VERIFYMC_PLATFORM_URL to this website’s HTTPS origin and VERIFYMC_BRIDGE_CREDENTIAL to your new credential in the connector’s private environment configuration.
  3. Run the included managed connector using node --env-file=.env.connector managed-start.mjs from the legacy folder.
  4. Connect Minecraft to the local Node.js server using /connect 127.0.0.1:8080.

The local connector checks platform authorization before starting. It renews a short lease and stops the Minecraft service if access is suspended, revoked, or unavailable. This keeps the native Minecraft connection format intact.

The local Minecraft command relay remains experimental. A direct cloud Minecraft connection address is not offered until it has been tested against your Bedrock version.

03. Verify in Minecraft

MINECRAFT · PRIVATE COMMANDS
# Connect your email
/verifymc email connect "your@email.com"

# Enter the code from your inbox
/verifymc otp <code>

# Check your verification
/verifymc status

Other commands: /verifymc otp resend_otp, /verifymc email disconnect, /verifymc help, and /verifymc website.

Use /verifymc:verifymc if the short command is unavailable. Quote email addresses when using a String argument; the supported API does not define a Message argument type.

What to know before a public rollout

Website accounts and player email verification are separate. The local prototype’s player tags are encoded, not encrypted, and the original email-disconnect operation has no fresh OTP check. Keep that relay in a controlled world until player identity and unlink confirmation are hardened.

Bridge credentials authorize the managed connector. They are revocable and stored as hashes in the platform database. The connector is not tamper-proof against someone who controls its host. Platform suspension revokes platform access; a host can still run their own independent local service.

“Online” means an authorized connector recently reported a Minecraft connection. It is not an independent uptime measurement or a count of verified players.