Home / Egress and tunnels
MCGateway
mcgateway.net/Bedrock console gateway (Xbox Live friend bot)egress/mcgatewayJSONcomparereport an errorprovider JSON
- Free allowance
- The core MCGateway transfer service is free and is intended to remain free.
- Verdict
- fails: egressdata cannot be read back out at a usable rate or price
- Cost
- not statedsee Price below
- Identity
- emailno card, no phone
- Binding limit
- noneno named constraint binds
- Evidence
- documented3 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-23checked 2026-10-23 (live); stale on 2026-11-23
| Free tier | The core MCGateway transfer service is free and is intended to remain free. unit none; metered on unstated |
|---|
| Price | USD 0 |
|---|
| Limits | - write-gated the transfer requires an access bot to accept a friend request first; no address is issued to the server owner source
|
|---|
| Binding | none There is no public address or port to meter, so no byte allowance is ever reached. The gate is the shape of the service: a player joins a bot's world and is transferred from inside the game. |
|---|
| Identity | email An Xbox Live account to friend the bot: 'Add an available MCGateway bot, wait for the automatic friend acceptance, then join MCGateway Hub.' No Microsoft password is asked for. |
|---|
| Egress | No byte allowance is published and none would apply: the service is a bot the player friends, not a port.; ingress: none free allowance: none published |
|---|
| Interface | unknown No API is described; access is through the Minecraft Friends tab and a Discord for server-owner tickets. |
|---|
| Tooling | Minecraft client only; no agent, no CLI |
|---|
| Composes with | Composes with any Bedrock host, including one behind another vendor's UDP tunnel, but adds nothing itself. |
|---|
| Reliability | Friend acceptance 'usually takes around 20 to 30 seconds and can take up to 60 seconds'; a stale Friends list needs a game restart; the bot fleet is the only path. |
|---|
| Notes | This is the Bedrock-specific answer was asked to find, and it is the inverse of what was wanted: a free way for a console player to reach an arbitrary Bedrock server, with no free public UDP endpoint handed to the server owner. It solves the console's missing address box, not the host's missing port. |
|---|
| Evidence note | documented The join flow is quoted in full on the front page; whether a server owner can obtain any address was checked on the front page only, and the detailed guide was not read. |
|---|
| Parsed numbers | |
|---|
Evidence 3
| date | source | what it proved |
|---|
| 2026-10-23 | mcgateway.net/ | 'Add an access bot, join the MCGateway Hub through your Friends tab, and choose where you want to go.' |
| 2026-10-23 | mcgateway.net/ | 'Open the Hub menu with the robot or Ender Pearl, choose Add Server, enter the Bedrock IP and port, then transfer.' The destination is dialled by the bot, not by the player |
| 2026-10-23 | mcgateway.net/ | 'The core MCGateway transfer service is free and is intended to remain free.' |
More fields 6
| wg path | none |
|---|
| wg detail | No WireGuard and no address to reach: the transfer runs inside Minecraft's Friends list. |
|---|
| ingress | none |
|---|
| volume stated | No byte allowance is published and none would apply: the service is a bot the player friends, not a port. |
|---|
| bytes transit | yes |
|---|
| transit note | The bot's Xbox Live session relays the player into the destination server. |
|---|
Unknown values 3
- interface: the access interface was not established
- per object cap stated: the field does not apply to this kind of offer
- retention stated: the field does not apply to this kind of offer