Minecraft server status checker

A status request performs a real protocol ping and hands back what the server answered: the resolved address and port, the motd with its colour codes plus a plain rawMotd, the version string and numeric protocol, onlinePlayers and maxPlayers, the round trip ping in milliseconds, and the favicon as a data URI.

Note that ping is the latency between the API host and the game server, not between you and either of them, and cachedAt tells you when the check was actually performed.

Java servers speak the TCP handshake protocol on port 25565 by default; Bedrock servers answer a RakNet ping on UDP 19132. The edition is a path parameter, so you get both through the same route shape and the same response document.

One consequence worth knowing: a Bedrock ping reports its version as something like MCPE rather than a semantic version, and its protocol number counts on a separate scale from Java's.

One GET request, one JSON document. Check online first, then read whatever you need - the fields for a live server are absent when it is offline.

curl -s "https://mc-api.io/server/JAVA/hypixel.net"

const response = await fetch("https://mc-api.io/server/JAVA/hypixel.net");
if (!response.ok) {  const { message } = await response.json();  throw new Error(message);}
const server = await response.json();console.log(server);

import requests
response = requests.get("https://mc-api.io/server/JAVA/hypixel.net", timeout=10)response.raise_for_status()
server = response.json()print(server)

HttpClient client = HttpClient.newHttpClient();HttpRequest request = HttpRequest.newBuilder(URI.create("https://mc-api.io/server/JAVA/hypixel.net")).build();
HttpResponse<String> response = client.sendAsync(request, BodyHandlers.ofString()).join();System.out.println(response.body());

Field-by-field documentation is in the server endpoint reference, and the icon endpoint sits next to it under Favicon.