MCAPI.TR Logo

Minecraft API Comparison

Compare server-status APIs by capability. The same table shows what MCAPI.TR supports and what it does not.

Last reviewed:

How we compared

We reviewed official API docs and provider product pages, and checked MCAPI.TR cells against its current code and endpoint contract. Undocumented does not mean confirmed absent. Dashboard features are provider claims, not account-based end-to-end tests. This is not a speed, uptime or market-share ranking.

Scope: Minecraft server status, Query, monitoring and related developer/media tools.

YesNoPartialUndocumented

51 / 51 features shown

Server API feature comparison · 2026-11-13
FeatureMCAPI.TRmcsrvstat.us
Protocols and connectivity
Java status lookup
Yes
Yes
Bedrock / RakNet
Yes
Yes
Legacy Java protocol
Yes
Partial
Details

Java 1.7+ or Query; no dedicated legacy ping documented.

Source
Automatic Java / Bedrock selection
Yes
Undocumented
Custom server port
Yes
Yes
DNS SRV resolution
Yes
Yes
Java UDP Query
Partial
Details

Optional query=true; software and plugins only.

Source
Yes
Separate Query port selection
No
No
Details

Docs require Query and game ports to match.

Source
Client-selectable timeout
No
Undocumented
Server data
Online and maximum players
Yes
Yes
Server-advertised player sample
Yes
Yes
Version and protocol data
Yes
Yes
MOTD content
Yes
Yes
Raw / clean / HTML MOTD
Yes
Yes
Numeric server latency
Yes
Undocumented
Query software / plugin data
Yes
Yes
Query map and extra game data
No
Yes
Forge / FML mod data
Partial
Details

Mod IDs are returned; mod versions are not preserved.

Source
Yes
Bedrock game mode and server ID
Yes
Yes
Mojang / EULA block flag
No
Yes
Freshness and diagnostics
Observation / cache timestamps
Yes
Yes
Explicit stale / last-good response
Yes
Undocumented
Machine-readable failure reason
Yes
Partial
Details

Protocol/debug flags, not an equivalent reason_code contract.

Source
DNS / protocol diagnostics
Yes
Yes
Dedicated HTTP-code-only server check
Partial
Details

Status JSON uses 200/404; no dedicated simple route.

Source
Yes
Discovery, history and monitoring
Multiple servers in one request
Yes
Undocumented
Paginated saved-server API
Yes
Undocumented
Paginated trend ranking
Yes
Undocumented
Automatic server monitoring
Yes
Undocumented
Player / status history
Yes
Undocumented
Discord / webhook downtime alerts
No
Undocumented
User-managed hosted status page
No
Undocumented
Media and tools
Direct server favicon image
Yes
Yes
Embeddable server status image
Yes
Undocumented
Status image appearance options
Yes
Undocumented
Transparent-background status image
No
Undocumented
SVG status badge
Yes
Undocumented
HTML iframe widget
Yes
Undocumented
Layered server-banner editor
Yes
Undocumented
Reusable saved-design API
Yes
Undocumented
MOTD → PNG endpoint
Yes
Undocumented
Server MOTD text editor
No
Undocumented
Developer features
Votifier vote sending / testing
No
Undocumented
Selective field retrieval
Yes
Undocumented
Published OpenAPI contract
Yes
Undocumented
Keyless public status API
Yes
Yes
JSON server status response
Yes
Yes
Plain-text scalar data routes
No
Undocumented
Official JavaScript / Node.js client
Yes
Undocumented
Official Go client
No
Undocumented
API service status page
Yes
Yes

Player samples, plugins and mod data depend on what the server exposes. Support does not guarantee a value for every server. Reported latency is not the end user’s connection ping.

Current MCAPI.TR limitations

These capabilities are absent or partial in the current version. This is not a roadmap or delivery commitment.

  • Java UDP QueryOptional query=true; software and plugins only.Partial
  • Separate Query port selectionNo
  • Client-selectable timeoutNo
  • Query map and extra game dataNo
  • Forge / FML mod dataMod IDs are returned; mod versions are not preserved.Partial
  • Mojang / EULA block flagNo
  • Dedicated HTTP-code-only server checkStatus JSON uses 200/404; no dedicated simple route.Partial
  • Discord / webhook downtime alertsNo
  • User-managed hosted status pageNo
  • Transparent-background status imageNo
  • Server MOTD text editorNo
  • Votifier vote sending / testingNo
  • Plain-text scalar data routesNo
  • Official Go clientNo

Service feature inventory

MCAPI.TR

Java, Bedrock and Legacy status API with catalog, history, diagnostics and embeddable media.

Protocols and connectivity

  • Java status lookup
  • Bedrock / RakNet
  • Legacy Java protocol
  • Automatic Java / Bedrock selection
  • Custom server port
  • DNS SRV resolution
  • Java UDP Query · PartialOptional query=true; software and plugins only.

Server data

  • Online and maximum players
  • Server-advertised player sample
  • Version and protocol data
  • MOTD content
  • Raw / clean / HTML MOTD
  • Numeric server latency
  • Query software / plugin data
  • Forge / FML mod data · PartialMod IDs are returned; mod versions are not preserved.
  • Bedrock game mode and server ID

Freshness and diagnostics

  • Observation / cache timestamps
  • Explicit stale / last-good response
  • Machine-readable failure reason
  • DNS / protocol diagnostics
  • Dedicated HTTP-code-only server check · PartialStatus JSON uses 200/404; no dedicated simple route.

Discovery, history and monitoring

  • Multiple servers in one request
  • Paginated saved-server API
  • Paginated trend ranking
  • Automatic server monitoring
  • Player / status history

Media and tools

  • Direct server favicon image
  • Embeddable server status image
  • Status image appearance options
  • SVG status badge
  • HTML iframe widget
  • Layered server-banner editor
  • Reusable saved-design API
  • MOTD → PNG endpoint

Developer features

  • Selective field retrieval
  • Published OpenAPI contract
  • Keyless public status API
  • JSON server status response
  • Official JavaScript / Node.js client
  • API service status page

Usage and caching

Single status: 120/min/IP. Bulk: 50 targets, 6 batches/min. Default status cache 60s; failures/stale can use 15s. Follow response timestamps.

Official sources reviewed

mcsrvstat.us

Combines Ping and Query; documents Java/Bedrock, mod/plugin data, an EULA flag and debug routes.

Protocols and connectivity

  • Java status lookup
  • Bedrock / RakNet
  • Legacy Java protocol · PartialJava 1.7+ or Query; no dedicated legacy ping documented.
  • Custom server port
  • DNS SRV resolution
  • Java UDP Query

Server data

  • Online and maximum players
  • Server-advertised player sample
  • Version and protocol data
  • MOTD content
  • Raw / clean / HTML MOTD
  • Query software / plugin data
  • Query map and extra game data
  • Forge / FML mod data
  • Bedrock game mode and server ID
  • Mojang / EULA block flag

Freshness and diagnostics

  • Observation / cache timestamps
  • Machine-readable failure reason · PartialProtocol/debug flags, not an equivalent reason_code contract.
  • DNS / protocol diagnostics
  • Dedicated HTTP-code-only server check

Media and tools

  • Direct server favicon image

Developer features

  • Keyless public status API
  • JSON server status response
  • API service status page

Usage and caching

Response cache: 5 minutes. A descriptive, nonempty User-Agent is required. No numeric request limit in the reviewed documentation.

Official sources reviewed

mcstatus.io

Alongside v2 status/image APIs, its dashboard advertises monitoring, history, event logs, status pages and webhooks.

Protocols and connectivity

  • Java status lookup
  • Bedrock / RakNet
  • Legacy Java protocol
  • Custom server port
  • DNS SRV resolution
  • Java UDP Query
  • Client-selectable timeout

Server data

  • Online and maximum players
  • Server-advertised player sample
  • Version and protocol data
  • MOTD content
  • Raw / clean / HTML MOTD
  • Query software / plugin data
  • Forge / FML mod data
  • Bedrock game mode and server ID
  • Mojang / EULA block flag

Freshness and diagnostics

  • Observation / cache timestamps
  • Machine-readable failure reason · Partialv2 errors return plain text.

Discovery, history and monitoring

  • Automatic server monitoringVia dashboard; a provider-published feature.
  • Player / status historyDashboard advertises history, uptime and event logs.
  • Discord / webhook downtime alerts
  • User-managed hosted status page

Media and tools

  • Direct server favicon image
  • Embeddable server status image
  • Status image appearance options
  • Transparent-background status image
  • Server MOTD text editor

Developer features

  • Votifier vote sending / testing
  • Keyless public status API · PartialDocumented v2 routes are keyless; the new dashboard API uses a token flow.
  • JSON server status response
  • Official JavaScript / Node.js client
  • Official Go client
  • API service status page

Usage and caching

v2 docs: 5 requests/s/IP, Java Query on by default, timeout up to 10s. The new dashboard has a separate token flow; v2 limits are not assumed for it.

Official sources reviewed

MineTools

Provides separate server Ping, Query and favicon endpoints, with an independently selectable Query port.

Protocols and connectivity

  • Java status lookup
  • Custom server port
  • Java UDP Query
  • Separate Query port selection

Server data

  • Online and maximum players
  • Server-advertised player sample
  • Version and protocol data
  • MOTD content
  • Numeric server latency
  • Query software / plugin data
  • Query map and extra game data

Freshness and diagnostics

  • Observation / cache timestamps · PartialCaching documented generally; Ping timing fields unspecified.

Media and tools

  • Direct server favicon image

Developer features

  • Keyless public status API
  • JSON server status response

Usage and caching

Caching and CORS are documented. Numeric server-endpoint quotas and a fixed TTL are not specified in the reviewed pages.

Official sources reviewed

Minecraft-API.com

Server Ping and Query families, including separate routes for state, player counts, MOTD, latency, favicon and version.

Protocols and connectivity

  • Java status lookup
  • Custom server port
  • Java UDP Query
  • Separate Query port selection

Server data

  • Online and maximum players
  • Version and protocol data
  • MOTD content
  • Raw / clean / HTML MOTD · PartialColored MOTD and JSON/text routes; not the same three-format contract.
  • Numeric server latency
  • Query software / plugin data
  • Query map and extra game data
  • Forge / FML mod data · PartialPing example includes FML modinfo; exact coverage unspecified.

Media and tools

  • Direct server favicon image

Developer features

  • Selective field retrieval · PartialSeparate field routes, not fields= projection in one response.
  • Keyless public status API
  • JSON server status response
  • Plain-text scalar data routes

Usage and caching

Ping/Query document JSON and text output. These pages do not specify a fixed cache duration or numeric request quota.

Official sources reviewed

MCAPI.us

Status, separate Query and status images, with a browser JavaScript helper and last-check/last-online times.

Protocols and connectivity

  • Java status lookup
  • Custom server port
  • Java UDP Query
  • Separate Query port selection

Server data

  • Online and maximum players
  • Server-advertised player sample · PartialThe separate Query route can provide player names.
  • Version and protocol data
  • MOTD content
  • Numeric server latency · Partialduration is API processing time, not game-server RTT.
  • Query software / plugin data
  • Query map and extra game data · PartialDetailed Query exists; no complete field schema published.

Freshness and diagnostics

  • Observation / cache timestamps
  • Explicit stale / last-good response · Partiallast_online exists; serving a last-good payload as stale is undocumented.
  • Machine-readable failure reason · PartialHas error/status fields; no structured reason enum documented.

Media and tools

  • Direct server favicon image · PartialIcon included in status image; standalone icon route undocumented.
  • Embeddable server status image
  • Status image appearance options

Developer features

  • Keyless public status API
  • JSON server status response
  • Official JavaScript / Node.js client

Usage and caching

Requests no more than once per client per minute. Results are cached for a few minutes; a field description mentions five-minute updates.

Official sources reviewed

About